Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: Groups which have new mails
Date: 20 Apr 1999 10:56:50 -0400	[thread overview]
Message-ID: <glmpv4zpcgd.fsf@faron.mitre.org> (raw)
In-Reply-To: Danny Siu's message of "19 Apr 1999 18:10:46 -0700"

Danny Siu <dsiu@Adobe.COM> writes:

>   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? 

Because read messages are read messages.   :-)

> I can't find better way of keeping the articles I need to re-visit
> or reply.

Between unread, read, ticked and dormant, I find that I have all I need.

> I use tick marks for articles I want to keep in the group till hell
> freezes.

This is what I use the dormant mark for.

I use the tick mark for articles that I have seen, but need to do
something with.

> 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.

For all of my normal mail groups, I use nnml.  It is the fastest
backend for opening large groups.

> I explicitly bind 'd' to gnus-summary-mark-as-expirable for article
> deletion.

I use total-expiry.  Read articles will eventually be deleted.

> All unread articles are the one I need to re-visit or reply.

For me, unread articles are unread.  Ticked messages still require
some action from me.

> Also, movement commands doesn't work well on read articles ('n'/'p'
> moves between unread articles only).

Right, and sometimes that is what you want.  If you want to move
between articles regardless of readedness, use N and P.

-- 
Justin Sheehy

In a cloud bones of steel.
  




  parent reply	other threads:[~1999-04-20 14:56 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
1999-04-20 14:56     ` Justin Sheehy [this message]
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=glmpv4zpcgd.fsf@faron.mitre.org \
    --to=justin@linus.mitre.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;
as well as URLs for NNTP newsgroup(s).