sup talk - Jan 2008 - archived threads not returning to inbox

I''m running sup-0.4 since this morning and I''ve noticed that
archived
threads that get new messages are not reappearing in my inbox.  I do
see the expected message: Loaded 1 new message, 1 to inbox. but the thread
doesn''t reappear.  If I quit and restart sup, then the thread does
correctly
reappear in the inbox.  I thought I was noticing this with other threads
so to test, I used my gmail account, sent a message to sup, received and 
archived it, and then replied to it again with my gmail account.

* John Bent [Wed Jan 23 18:12:37 -0500 2008]:
> I''m running sup-0.4 since this morning and I''ve noticed
that archived
> threads that get new messages are not reappearing in my inbox.  I do
> see the expected message: Loaded 1 new message, 1 to inbox. but the thread
> doesn''t reappear.  If I quit and restart sup, then the thread does
correctly
> reappear in the inbox. 
Sup needs some work still on keeping buffers up to date. Try hitting
''@'' to
refresh your inbox.

Reformatted excerpts from John Bent''s message of
2008-01-23:
> I''m running sup-0.4 since this morning and I''ve noticed
that archived
> threads that get new messages are not reappearing in my inbox.  I do
> see the expected message: Loaded 1 new message, 1 to inbox. but the
> thread doesn''t reappear.  If I quit and restart sup, then the
thread
> does correctly reappear in the inbox.
I think I''ve fixed this in next, with commit
81794a14968410f70ee0563afcf3b1e7e90be101.

Care to try?

-- 
William <wmorgan-sup at masanjin.net>

Excerpts from William Morgan''s message of Thu Jan 24 19:54:02 -0700
2008:
> Reformatted excerpts from John Bent''s message of 2008-01-23:
> > I''m running sup-0.4 since this morning and I''ve
noticed that archived
> > threads that get new messages are not reappearing in my inbox.  I do
> > see the expected message: Loaded 1 new message, 1 to inbox. but the
> > thread doesn''t reappear.  If I quit and restart sup, then the
thread
> > does correctly reappear in the inbox.
> 
> I think I''ve fixed this in next, with commit
> 81794a14968410f70ee0563afcf3b1e7e90be101.
> 
> Care to try?
> 
It works.  Thanks!