info-gnus-english
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On the best practices


From: Kai Grossjohann
Subject: Re: On the best practices
Date: Tue, 11 May 2004 09:04:07 +0200
User-agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.2 (gnu/linux)

Xavier Maillard <zedek@gnu-rox.org> writes:

> On  7 May 2004, Kai Grossjohann wrote:
>
>> I suggest to make them dormant, if you don't want to see them.
>
> Hmm. This is not exactly what I meant :) They are useless (or almost) in
> the  current group but  I like  sometimes to  be able  to read  old past
> articles.

It seems to me that dormant articles will do this, and if total-expire
is off, read articles will also do this.

>> (The meaning of dormant is "hidden until a followup appears", and that
>> seems to be pretty much exactly what you want.)
>
> Hmm, ok,  but there is little chance  someone will post a  followup to a
> '96 post ;) So then, how can I see them again ? Using '/' in summary ?

Yes, `/ D' will show the dormants.

>> Of, if total-expire is off, just mark them as read. That's what I
>
> That is an idea but I sometimes,  force, catch-up on groups and I fear I
> would certainly  loose my  ticked/read articles  if I would  do it  on a
> wrong group, right ?

I don't know about *force* catch-up, but just hitting `c' on a group
is normally not dangerous:

- It never marks ticked or dormant articles for deletion.
- If auto-expire for that group is on, it marks articles E
  (expirable).
- If auto-expire is off, it marks articles as read.  (But this will
  make them expirable if total-expire is on.)

So if normal reading (ie, selecting an article to show it) would make
an article be marked for deletion later on (because of total-expire or
auto-expire), then catchup will also do that, and if normal reading
does *not* mark it for deletion later, then neither will catchup.

>> do.  It's quite quick, even with a thousand messages in a group that
>> are marked as read.
>
> Hmm, I have to say, I can't choose how to deal with that ;)

?

Kai



reply via email to

[Prev in Thread] Current Thread [Next in Thread]