Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: No way to make a given single article un-unseen !
Date: Tue, 24 Apr 2012 18:03:42 +0900	[thread overview]
Message-ID: <b4my5pljyc1.fsf@jpl.org> (raw)
In-Reply-To: <87fwbtlnax.fsf@topper.koldfront.dk>

Adam Sjøgren wrote:
> On Tue, 24 Apr 2012 13:19:46 +0900, Katsumi wrote:
>> I vaguely think it would be convenient to make the unseen marks remain
>> unless those bodies have been read, though.

> Wouldn't that make "seen" (~"has it ever been shown in a summary") equal
> to "read" (~"has the article been displayed")?

Though I don't know what one who introduced `seen' and `unseen'
intended, I think there are two kinds of unread articles.  One
is read only at a glance but marked as unread to read throughly
in the future, and the other has never been read at all.  The
former is a business mail that is troublesome to read but should
never ignore, for example.  To mark it as ticked differs; that is
used for the future reference.  So, I wish there were two kinds
of unread marks, and guessed `seen' and `unseen' may possibly be
able to be the very things.



  reply	other threads:[~2012-04-24  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  3:27 jidanni
2012-04-24  4:19 ` Katsumi Yamaoka
2012-04-24  5:19   ` Adam Sjøgren
2012-04-24  9:03     ` Katsumi Yamaoka [this message]
2012-04-24  9:51       ` Steinar Bang
2012-04-24 10:00       ` Adam Sjøgren
2012-04-24 10:44         ` Katsumi Yamaoka
2012-04-25 12:27           ` jidanni
2012-04-25 18:34             ` Peter Münster
2012-04-25 19:20             ` Carson Chittom
2012-05-07  4:02               ` jidanni
2012-06-10 20:33                 ` 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=b4my5pljyc1.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).