From: Tony Bennett <TBennett@nvidia.com>
Subject: Re: nnimap: any way to update server from summary buffer without getting new mail?
Date: Wed, 30 Oct 2002 09:49:54 -0500 [thread overview]
Message-ID: <m3k7k0m165.fsf@uh-oh.nvidia.com> (raw)
In-Reply-To: <iluwuo09eit.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 30 Oct 2002 15:39:54 +0100")
Simon Josefsson <jas@extundo.com> writes:
> tbennett@nvidia.com (Tony E. Bennett) writes:
>
>> oort 0.07
>>
>> I use tkbiff to show me "unread" msgs on my nnimap:INBOX.
>>
>> As long as I stay in the summary buffer, tkbiff will still
>> display the msgs I just read as "unread".
>>
>> Is there any command I can run from summary buffer that will
>> flush out changes to the imap server so the msgs get marked
>> as "read"?
>
> Does M-g work?
Yes, it does work, but is relatively slow and "screen-flashy" enough
that it is annoying at times.
Hoping to have something that just does the server update and
doesn't pull in any new mail...
--tony
next prev parent reply other threads:[~2002-10-30 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 1:20 Tony E. Bennett
2002-10-30 14:39 ` Simon Josefsson
2002-10-30 14:49 ` Tony Bennett [this message]
2002-11-12 19:09 ` Tony E. Bennett
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=m3k7k0m165.fsf@uh-oh.nvidia.com \
--to=tbennett@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).