Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: marking articles when reading them
Date: Fri, 7 Jul 2000 17:12:45 +0200	[thread overview]
Message-ID: <vafituias9e.fsf@lucy.cs.uni-dortmund.de> (raw)

Right now, reading a message marks it as read (or expirable, if
auto-expire is turned on, but I won't be talking about auto-expire for
the moment).

Of course, that's just the way that Gnus operates: it pretends your
mail is like news, and so reading a message should make it go away,
sort of.

But new Gnus users might not want this behavior.  For them, it would
be useful to tell Gnus to, say, tick a message when it is read, rather
than marking it as read.

I suggest the following: introduce a variable
`gnus-select-article-mark' (or somesuch).  This variable defaults to
gnus-read-mark.  And the functions gnus-summary-mark-unread-as-read
and gnus-summary-mark-read-and-unread-as-read use that variable rather
than the hard-coded gnus-read-mark.

Since this variable can be set in a group-local fashion, it would be
easy for users to define `important' mail groups, where the default
would be to keep the message when it is read.  And in mail groups that
contain mailing lists, the default behavior can be kept.

I used to use a similar behavior for a year or so (in the olden days
of (ding) Gnus), and a colleague still uses it.

What do you all think?

kai

PS: Should the variable be a group parameter for easy customization
    with `G c'?
-- 
I like BOTH kinds of music.



             reply	other threads:[~2000-07-07 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 15:12 Kai Großjohann [this message]
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
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=vafituias9e.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.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).