Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: marking articles when reading them
Date: 01 Nov 2000 00:32:03 +0100	[thread overview]
Message-ID: <vafitq8zix8.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <q6mhf5sreto.fsf@spartacus.utdallas.edu>

On 31 Oct 2000, amos+lists.ding@utdallas.edu wrote:
> 
> kg> I suggest the following: introduce a variable
> kg> `gnus-select-article-mark' (or somesuch).  This variable
> kg> defaults to gnus-read-mark.  And the functions
> kg> gnus-summary-mark-unread-as-read and
> kg> gnus-summary-mark-read-and-unread-as-read use that variable
> kg> rather 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?

It would tick all messages that a user selects for reading.

The consequence is that there are the following marks:

space -- the user hasn't seen this message yet, it's new, fresh
`!' -- the user has read the message
`E' -- the user has marked the message for deletion
`r' -- user has read the message, wants to keep it but not show

I think that this is mostly what a run-of-the-mill mail reader does.
For example, I think VM marks fresh messages with `N', read messages
with space, and I'm not sure about the deletion mark.  A
run-of-the-mill mail reader might not have an equivalent of the Gnus
`r' mark, though.

This is crippling Gnus, I know.  But if it makes people happy...

kai
-- 
I like BOTH kinds of music.



      reply	other threads:[~2000-10-31 23:32 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
2000-10-31 23:32   ` Kai Großjohann [this message]

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=vafitq8zix8.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    /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).