From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: marking articles when reading them
Date: 31 Oct 2000 13:27:47 -0600 [thread overview]
Message-ID: <q6mhf5sreto.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <vafituias9e.fsf@lucy.cs.uni-dortmund.de>
>>>>> On Fri, 7 Jul 2000 17:12:45 +0200,
>>>>> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> (kg) writes:
kg> Right now, reading a message marks it as read (or expirable, if
kg> auto-expire is turned on, but I won't be talking about auto-expire for
kg> the moment).
kg> Of course, that's just the way that Gnus operates: it pretends your
kg> mail is like news, and so reading a message should make it go away,
kg> sort of.
kg> But new Gnus users might not want this behavior. For them, it would
kg> be useful to tell Gnus to, say, tick a message when it is read, rather
kg> than marking it as read.
Must admit, when first using gnus/nnimap for mail reading, this did
take some getting used to.
kg> I suggest the following: introduce a variable
kg> `gnus-select-article-mark' (or somesuch). This variable defaults to
kg> gnus-read-mark. And the functions gnus-summary-mark-unread-as-read
kg> and gnus-summary-mark-read-and-unread-as-read use that variable rather
kg> than the hard-coded gnus-read-mark.
Would that then tick all read messages? If so, wouldn't that negate
the usefulness of having such a flag? Or perhaps you're meaning yet
another read-but-dont-submerge flag?
--
Amos
next prev parent reply other threads:[~2000-10-31 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 15:12 Kai Großjohann
2000-07-07 15:37 ` David S. Goldberg
2000-07-07 16:57 ` Kai Großjohann
2000-10-31 19:51 ` Amos Gouaux
2000-10-31 23:35 ` Kai Großjohann
2000-11-01 20:20 ` Amos Gouaux
2000-11-02 10:18 ` Kai Großjohann
2000-11-09 3:47 ` Amos Gouaux
2000-07-07 16:03 ` François Pinard
2000-10-31 19:27 ` Amos Gouaux [this message]
2000-10-31 23:32 ` Kai Großjohann
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=q6mhf5sreto.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/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).