From: David Abrahams <dave@boost-consulting.com>
Subject: Re: Mark all as read? (nnimap?)
Date: Sat, 12 Feb 2005 16:08:08 -0500 [thread overview]
Message-ID: <uk6pdcwqv.fsf_-_@boost-consulting.com> (raw)
In-Reply-To: <y68d5v97jz7.fsf@contents-vnder-pressvre.mit.edu>
David Z Maze <dmaze@MIT.EDU> writes:
> David Abrahams <dave@boost-consulting.com> writes:
>
>> Can someone please explain the differences between
>>
>> 1) `c' in the summary buffer
>> 2) `Z C' in the summary buffer
>
> 'C-h c' and 'C-h Z C' are informative: 'c' marks all unread messages
> as read, 'Z C' marks all messages (read, unread, ticked, whatever) as
> read.
>
>> 3) `C' in the group buffer
>>
>> I really expected 2 and 3 to be equivalent, but #2 actually makes no
>> change in the number of articles marked unread in the group buffer.
>
> I'd kind of expect (2) and (3) to be the same as well. You can also
> run 'c' from the group buffer, which has the same effect as running it
> from the summary buffer. I don't think I've ever actually used the
> capital-C variants.
Another data point: in the group buffer, it's very common for me to do
`c' on an nnimap group, and see the number of unread messages go to
zero, as one would expect. But if I follow that with `g', the
number of unread messages returns to the old value. That's why I tend
to use the big `C' hammer. The whole experience is really flaky.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
prev parent reply other threads:[~2005-02-12 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 16:12 Mark all as read? David Abrahams
2005-02-09 16:53 ` David Z Maze
2005-02-12 21:08 ` David Abrahams [this message]
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=uk6pdcwqv.fsf_-_@boost-consulting.com \
--to=dave@boost-consulting.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).