From: grant@antiflux.org (Grant Hollingworth)
Subject: [sup-talk] archived threads not returning to inbox
Date: Wed, 23 Jan 2008 19:07:12 -0500 [thread overview]
Message-ID: <1201133186-sup-902@spooky.local> (raw)
In-Reply-To: <1201129847-sup-6955@tangerine.lanl.gov>
* 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.
next prev parent reply other threads:[~2008-01-24 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 23:12 John Bent
2008-01-24 0:07 ` Grant Hollingworth [this message]
2008-01-25 2:54 ` William Morgan
2008-01-25 5:13 ` John Bent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201133186-sup-902@spooky.local \
--to=grant@antiflux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox