Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Moving articles destroys all marks
Date: 05 Oct 1999 10:28:25 +0200	[thread overview]
Message-ID: <vafr9jaus7q.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: =?iso-8859-1?q?Fran=E7ois?= Pinard's message of "04 Oct 1999 16:23:58 -0400"

François Pinard <pinard@iro.umontreal.ca> writes:

> By all means, I would like that moved articles recover their "unread" status.
> What is the purpose of moving articles that Gnus would carefully keep out
> of my sight (unless I take extraordinary measures to read them)?

Just for the record: I am very much used to articles staying the way
they are after being moved.  I hit M-u before moving an article if I
want it to be unread after moving.  But often, I receive a message in
my default inbox, I then deal with it, and move it to another group
for archival.  (I can't use splitting for all messages; doing the
split correctly would be AI-complete.)

kai
-- 
Life is hard and then you die.


  parent reply	other threads:[~1999-10-05  8:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-01 11:04 Toni Drabik
1999-10-01 13:11 ` Robert Epprecht
1999-10-01 15:00   ` Toni Drabik
1999-10-01 20:52     ` Kai Großjohann
1999-10-03 14:57       ` Toni Drabik
1999-11-06  2:38     ` Lars Magne Ingebrigtsen
1999-11-06 16:02       ` Hrvoje Niksic
1999-10-04 20:23 ` François Pinard
1999-10-04 21:38   ` David S. Goldberg
1999-10-05 11:39     ` Kai Großjohann
1999-10-05 12:12       ` David S. Goldberg
1999-10-05 14:41         ` François Pinard
1999-10-05 16:40           ` Kai Großjohann
1999-10-05 17:30             ` David S. Goldberg
1999-10-05 17:48             ` François Pinard
1999-10-05  8:28   ` Kai Großjohann [this message]
1999-10-06 18:10   ` Toni Drabik

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=vafr9jaus7q.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).