From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Gnus Limits and catchup
Date: 26 Mar 1996 04:49:44 +0100 [thread overview]
Message-ID: <w8sohpky0mf.fsf@aegir.ifi.uio.no> (raw)
In-Reply-To: <rjd9617ets.fsf@babbage.dina.kvl.dk>
abraham@dina.kvl.dk (Per Abrahamsen) writes:
> I think catchup in the summary buffer should only affect the visible
> articles.
That makes sense. On the other hand, it can be convenient to have `c'
really do a normal catchup. For instance, you may have `expunge' in
the score file, and use `c' to mark the unseen articles as read. (The
reason for not using `mark-and-expunge' might be that one would want
to `/ w' once in a while and read the articles that one would normally
expunge.)
I don't know what would be most logical, though.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-03-26 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-25 8:32 Per Abrahamsen
1996-03-26 3:49 ` Lars Magne Ingebrigtsen [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=w8sohpky0mf.fsf@aegir.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).