From: Tim Landscheidt <tim@tim-landscheidt.de>
To: ding@gnus.org
Subject: Re: auto auto-expirable
Date: Mon, 01 Jun 2009 12:47:50 +0000 [thread overview]
Message-ID: <m3ljocdssp.fsf@lockfix.tim-landscheidt.de> (raw)
In-Reply-To: <b4my6scjj4v.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>>> Sometimes the scripts assign a message to the wrong folder. Currently,
>>> I just save the message to the correct folder and then deal with it
>>> while reading that other folder.
>>> Now, if I understand your proposal, it sounds like I would need to
>>> remember to clear the "expirable" mark before saving the message. If
>>> that's correct, it seems awkward and easy to forget to do.
>> When I face such situations, I usually move the article to the correct
>> group *before* reading it, so Katsumi's change would not affect you. In
>> the cases when the article is displayed for whatever reason, I also
>> usually M c it (before reading it), move it, and again read it from the
>> correct group.
> I'll do it like Didier, but I can agree with Mike. Maybe it
> will be better not to change the present behavior by default.
> [...]
I *think* I do it like Didier, but I don't know if I don't
do it sometimes like Mike :-). With the danger of losing
mail, I'd prefer a "Are you really sure?" dialog, perhaps
similar to scroll-left & Co. if technically possible.
In the end, moving a mail only to have it expired seems
not a very common thing to do.
Tim
next prev parent reply other threads:[~2009-06-01 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 11:19 Katsumi Yamaoka
2009-05-29 12:08 ` Didier Verna
2009-06-01 3:36 ` Mike Kupfer
2009-06-01 8:35 ` Didier Verna
2009-06-01 11:20 ` Katsumi Yamaoka
2009-06-01 12:47 ` Tim Landscheidt [this message]
2009-06-02 2:23 ` Mike Kupfer
2009-06-02 11:12 ` Katsumi Yamaoka
2009-06-02 11:38 ` Katsumi Yamaoka
2009-06-04 4:13 ` Mike Kupfer
2009-06-13 14:22 ` Tim Landscheidt
2009-08-12 8:28 ` Katsumi Yamaoka
2009-06-02 17:34 ` Reiner Steib
2009-06-05 12:34 ` Greg Troxel
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=m3ljocdssp.fsf@lockfix.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--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).