Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Subject: Soups and marks
Date: 16 Jun 1996 19:48:34 +0200	[thread overview]
Message-ID: <vafohmjabd9.fsf@ls6.informatik.uni-dortmund.de> (raw)

Hi all,

I have begun to brew soups.  While this is rather nice, I do have one
minor problem.  When brewing a soup, Gnus by default marks all souped
articles as read.  I would like to have control over the articles that
will be deleted, however (often I want to keep souped articles), and
as I use total-expire, marking them as read is not quite what I want.

I have therefore set gnus-souped-mark to ?\? (dormant) which works
rather nicely, mostly.  However, I have found out that I have to
retrieve all of a group in order to see the dormant articles.  Is
there a better way?

I know that acutally, the articles are marked ?F, but it seems that
Gnus thinks these are read, as well, when I reenter a group after
brewing soups.

I have also tried ?\  (unread), but that didn't allow me to
distinguish between unread articles that have already been souped and
those that haven't.

I can't use ?! as I use that for articles where I know I want to keep
them.  (For souped articles, I don't know yet.)  Wouldn't be able to
distinguish between souped and other articles there, either.

Can anyone give me a hand here?  Should I convert to auto-expire
rather than total-expire in order to have the `read' mark left over
for such things?

Thanks in advance for any hint you might be able to give.
kai
-- 
Life is hard and then you die.



             reply	other threads:[~1996-06-16 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-16 17:48 Kai Grossjohann [this message]
1996-06-17  2:22 ` Lars Magne Ingebrigtsen
1996-06-17 14:01   ` Kai Grossjohann
1996-06-17 16:20     ` Lars Magne Ingebrigtsen

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=vafohmjabd9.fsf@ls6.informatik.uni-dortmund.de \
    --to=grossjoh@charly.informatik.uni-dortmund.de \
    /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).