From: craffert@sps.ml.com (Colin Rafferty)
Cc: shrode@wsc.com
Subject: Re: Persistent News Articles - Saving News
Date: Tue, 5 Dec 95 10:15:29 EST [thread overview]
Message-ID: <9512051515.AA23530@sparc10.sps.ml.com> (raw)
In-Reply-To: Kai Grossjohann's message of Tue, 5 Dec 95 08:38:17 +0100
Kai Grossjohann writes:
>>>>>> On Tue, 5 Dec 95 02:03:30 -0500, Jason Schroeder
>>>>>> <shrode@wsc.com> said:
Jason> It would seem to me that if I want to save an article in
Jason> comp.lang.ml, for example, I would probably like to just keep
Jason> the article in the organization it has been initially
Jason> presented to me. So saving an article becomes the functional
Jason> equivalent of making the article persistent in that
Jason> newsgroup.
> I think the variable gnus-use-cache has a wrong name and doc string,
> for what we really use it for is to keep news articles in groups
> locally, don't we all?
> Jason, setting gnus-use-cache to t then ticking (`u') articles in news
> groups means they will remain in the news group forever (well, until
> you untick them, anyway).
I agree with Kai. I do this all the time, except rather than setting
them as unread (`!'), I prefer to set them as dormant (`?'). The
advantage of dormant over unread is that I don't see the articles unless
I want to (either as a `*' in the summary, or in the group itself). I
can always `M D' to show the dormants.
I also use this on my auto-expire mail groups.
Nit to pick with Lars: When I `M D', the articles are not threaded
correctly, and have no `A r' property (which I assume is a related
issue).
-Colin
next prev parent reply other threads:[~1995-12-05 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-05 7:03 Jason Schroeder
1995-12-05 7:38 ` Kai Grossjohann
1995-12-05 15:15 ` Colin Rafferty [this message]
1995-12-06 5:05 ` Lars Magne Ingebrigtsen
1995-12-08 18:28 ` Steven L. Baur
1995-12-08 20:29 ` Sten Drescher
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=9512051515.AA23530@sparc10.sps.ml.com \
--to=craffert@sps.ml.com \
--cc=craffert@ml.com \
--cc=shrode@wsc.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).