Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@sharedlists.com>
Cc: ding@gnus.org
Subject: Re: Marking for agent download unmarks as read
Date: Wed, 02 Oct 2002 21:36:07 -0700	[thread overview]
Message-ID: <sdlm5gxhoo.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <ilur8f8tu3z.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 02 Oct 2002 23:21:20 +0200")

>>>>> On Wed, 02 Oct 2002 23:21:20 +0200, Simon Josefsson <jas@extundo.com> said:

>> Why does the Agent remove `read' marks when using J # or @ to mark an
>> article for download?

Simon> I didn't look at the code, but is this unwanted behaviour?  If
Simon> you want to download the article, you don't want it marked as
Simon> read, do you?

Yes, actually I do some of the time at least.  The way I treat many of
my folders is that I have display set to !expired, and hence I see all
the old messages.  unread in these folders really means "needs a
response", and read really means "kept around for informational
purposes, or things that I need to look at but aren't crucial".  It's
a way of prioritizing, if you want to look at it another way.  ticked
= high, unread = medium, read = low.  My work boxes, inboxes, etc are
this way and has forced expiry on it.

The problem is that when I want to go offline I actually do want
unread stuff to, but I certainly don't want the read mark to go away.

-- 
"The trouble with having an open mind, of course, is that people will
 insist on coming along and trying to put things in it."   -- Terry Pratchett



  reply	other threads:[~2002-10-03  4:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 20:46 Kai Großjohann
2002-10-02 21:21 ` Simon Josefsson
2002-10-03  4:36   ` Wes Hardaker [this message]
2002-10-03  9:57   ` Kai Großjohann
2002-10-03 17:32 ` Kai Großjohann
2002-10-03 23:53   ` Wes Hardaker
2002-10-04  6:35     ` 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=sdlm5gxhoo.fsf@wanderer.hardakers.net \
    --to=wes@sharedlists.com \
    --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).