From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: Groups which have new mails
Date: 20 Apr 1999 11:25:17 +0200 [thread overview]
Message-ID: <vafpv4z4paa.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Danny Siu's message of "19 Apr 1999 18:10:46 -0700"
Danny Siu <dsiu@Adobe.COM> writes:
> I wonder how people use marks on mail groups for the purpose of
> keeping articles and indicating an need-to-be-late article.
I'm not a Gnus expert, but here's what I do:
I do not use total-expire. Fresh articles are unmarked. After I read
a message, I decide what I want to do with it:
- If it's a todo item for me, I tick it.
- If I want to keep it, it stays marked as read.
- If I want to delete it, I mark it as expirable.
This way, the Group buffer only shows groups with articles that I need
to deal with. Also, after entering a group, I only see messages that
I need to deal with (plus the ones from gnus-fetch-old-headers being
t, which provide context), and I can quickly tell the new ones from
the ones I've already seen before.
As to moving, you have n/p which move to an unmarked article, and N/P
which consider read articles, too. But moving could be improved.
As to reading lots of old articles being slow, well, I usually provide
a limit (as in `2 2 2 RET' from the Group buffer or `9 9 M-g' from the
Summary buffer).
Oh, yes, I have modified the group line format to show the number of
ticked/dormat messages (%i) as well as the number of unticked unread
messages (%y).
kai
--
Abort this operation? [Abort] [Cancel]
next prev parent reply other threads:[~1999-04-20 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-19 21:43 Danny Siu
1999-04-19 22:15 ` François Pinard
1999-04-19 22:40 ` Justin Sheehy
1999-04-20 1:10 ` Danny Siu
1999-04-20 9:25 ` Kai.Grossjohann [this message]
1999-04-20 14:56 ` Justin Sheehy
1999-04-20 19:26 ` Danny Siu
1999-04-20 20:35 ` Matt Armstrong
1999-04-20 9:27 ` Kai.Grossjohann
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=vafpv4z4paa.fsf@ramses.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).