Re: Soups and marks

[Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>]

>>>>> Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de>
>>>>> writes:

  Kai> [...] When brewing a soup, Gnus by default marks all souped
  Kai> articles as read. [...]

>>>>> On 17 Jun 1996 04:22:32 +0200, Lars Magne Ingebrigtsen
>>>>> <larsi@ifi.uio.no> said:

  Lars> Well, they will probably be read, so marking them as such is
  Lars> probably the most sensible thing.

Yes.  No.  I argue as follows:

Usually there two kinds of `read' messages: those that you want to
delete and those that you want to keep.  Without total-expire, the
ones to delete are the `expirable' ones, the ones to keep the `read'
ones.  With total-expire, the ones to delete are the `read' ones
whereas the ones to keep will be `ticked' or `dormant' (I suppose).

In both cases you have two kinds of messages but with your process
they're both marked the same way.  --> Conflict.

My suggestion was to mark them specially so that the user can look at
them and assign the correct mark intellectually.  (If you can't
program it, let the user do it.)

But your suggestion of taking note of the unread messages is really
nice and could rather simply be adapted to save all marks, I guess.  I
think I'll be doing this, in fact.

kai
-- 
Life is hard and then you die.