From: Danny Siu <dsiu@Adobe.COM>
Subject: Re: Groups which have new mails
Date: 19 Apr 1999 18:10:46 -0700 [thread overview]
Message-ID: <yj9iuasqep5.fsf@adobe.com> (raw)
In-Reply-To: Justin Sheehy's message of "19 Apr 1999 18:40:38 -0400"
Justin Sheehy writes:
Justin> Danny Siu <dsiu@Adobe.COM> writes:
>> WIBNI one could list only the groups which has new mails? This makes
>> mail reading much easier if you have tons of mail groups.
Justin> That is how it works for me, without modification.
Justin> Only groups with unread messages appear in the Group buffer.
Justin> Unread messages are close enough to 'new' messages that this is
Justin> basically the same thing. I define 'new' as "things I haven't
Justin> seen yet".
Guess we have a different definition of 'new' mails. By 'new' mails I mean
mails that just get incorporated by doing 'g'.
Justin> You don't do something silly like keeping messages that you've
Justin> read marked as unread, do you? ;-)
That is exactly what I do. Why not? I can't find better way of keeping the
articles I need to re-visit or reply. I know about the read marks and tick
mark. I use tick marks for articles I want to keep in the group till hell
freezes. I don't use read marks at all because 'C-u SPC' (to see all
articles) on a group with many articles is VERY slow (at least for nnfolder
anyways. see <yj9u2uzu83y.fsf@adobe.com>). I explicitly bind 'd' to
gnus-summary-mark-as-expirable for article deletion. All unread articles
are the one I need to re-visit or reply. Also, movement commands doesn't
work well on read articles ('n'/'p' moves between unread articles only).
I think you are right in <glmlngbwzji.fsf@caffeine.mitre.org>; I haven't
fully adjusted to the Gnus Way of reading mail after 4 years of using it.
I wonder how people use marks on mail groups for the purpose of keeping
articles and indicating an need-to-be-late article.
Any Gnus experts wanna speaks up here?
--
Danny Dick-Fung Siu mailto:dsiu@adobe.com
Acrobat Engineering @ Adobe Systems Incorporated
next prev parent reply other threads:[~1999-04-20 1:10 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 [this message]
1999-04-20 9:25 ` Kai.Grossjohann
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=yj9iuasqep5.fsf@adobe.com \
--to=dsiu@adobe.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).