Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Subject: Re: Moving articles destroys all marks
Date: 05 Oct 1999 10:41:08 -0400	[thread overview]
Message-ID: <oqu2o5an0b.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: dsg@mitre.org's message of "05 Oct 1999 08:12:06 -0400"

dsg@mitre.org (David S. Goldberg) writes:

> I like the simple approach we have now; whatever marks are associated
> with the article are preserved across the move.

The simplicity is always attractive, granted.

For a long while, I've been using Gnus without marking articles as "read"
automatically on first visit, preferring to have full control over when
I really want an article to disappear out of sight.  A very instructive
thread on `ding' convinced me to try otherwise, and by now, I'm glad to
have made that move.  Oh, it is still a little irritating having to `M-u'
so often, but yet, overall, there is less typing now.  The only drawback,
and it was a serious one for me, is how easily I was "loosing" articles
while moving them around (and I do move articles a lot :-).  Forget to
`M-u', and you're done: you even have to fight a bit to recover the article
immediately, if you happen to notice your mistake.  If you do not notice,
you've just lost an article for all practical purposes.  A single mistake,
you loose more than all the time you saved by the change of paradigm, at
least for that day.  Better _never_ make mistakes, but that's too much of
a pressure for the little me, I am loosing an important part of my comfort.

My need is simple: to be sure I do not loose articles while moving them
elsewhere.  In my case, the automatic reading that comes with opening an
article is plain unwelcome when the article has to be sorted elsewhere.
My feeling is that this automatic reading should be undone, automatically as
much as possible -- so I just cannot forget to do it.  Whatever scheme that
let me sort articles as I want, and is not error-prone, is acceptable to me.

My suggestion to "unread" before moving comes from that need.

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



  reply	other threads:[~1999-10-05 14:41 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 [this message]
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=oqu2o5an0b.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    /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).