From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: losing expirable mark after move
Date: Sun, 09 Jan 2011 22:14:47 +0900 [thread overview]
Message-ID: <b4mfwt2rzg8.fsf@jpl.org> (raw)
In-Reply-To: <87r5cmpgo7.fsf@micropit.couberia.bzh>
pmlists@free.fr (Peter Münster) wrote:
> When moving a message from one group to another, the expirable mark gets
> lost, even with gnus-preserve-marks = t.
> Is this wanted or a bug? How can I keep the expirable mark when moving?
(info "(gnus)Expiring Mail")
The expirable marks of articles will be removed when copying or
moving them to a group in which auto-expire is not turned on. This is
for preventing articles from being expired unintentionally. On the
other hand, to a group that has turned auto-expire on, the expirable
marks of articles that are copied or moved will not be changed by
default. I.e., when copying or moving to such a group, articles that
were expirable will be left expirable and ones that were not expirable
will not be marked as expirable. So, even though in auto-expire
groups, some articles will never get expired (unless you read them
again). If you don't side with that behavior that unexpirable articles
may be mixed into auto-expire groups, you can set
`gnus-mark-copied-or-moved-articles-as-expirable' to a non-`nil' value.
In that case, articles that have been read will be marked as expirable
automatically when being copied or moved to a group that has
auto-expire turned on. The default value is `nil'.
next prev parent reply other threads:[~2011-01-09 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 9:31 Peter Münster
2011-01-09 13:14 ` Katsumi Yamaoka [this message]
2011-01-09 13:51 ` gnus-manual-a4.pdf out of date (was: Re: losing expirable mark after move) Peter Münster
2011-01-11 18:52 ` gnus-manual-a4.pdf out of date 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=b4mfwt2rzg8.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).