Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: Moving articles destroys all marks
Date: 04 Oct 1999 16:23:58 -0400	[thread overview]
Message-ID: <oqso3qri1t.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Toni Drabik's message of "01 Oct 1999 13:04:44 +0200"

Toni Drabik <tdrabik@public.srce.hr> writes:

> This morning I just moved several hundred articles from one `nnfolder'
> group to another (which didn't exist before, and was created when doing
> `B m').  After doing `F' in *Group* buffer after that, I was unpleasantly
> surprised to see that all articles in the new group appeared as unread
> and without any other marks that were applied to them in the old group
> (i.e. ticked articles became ordinary ones, and all `A' marks were
> lost, too).

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)?

I would grant that Saved or Answered status be kept with the article while
they get moved.  But definitely, I would not like any read mark on them.
The status of being tickled or dormant might be preserved or lost, yet I
would vote for loosing these, given the choice.  I definitely decide afresh
for every moved article how I want it to get lost: when moving an article,
the last thing I want is to virtually loose it, as it does not get shown.

I made a few local patches to my copy of Gnus, still 0.95, trying to erase
"readness" just before moving.  It was unbearable before.  So, I receive as
very good news that Gnus does recover the unread status spontaneously, now.
I would be tempted to call a bug whenever it does otherwise...

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard



  parent reply	other threads:[~1999-10-04 20:23 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 [this message]
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
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=oqso3qri1t.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --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).