From: Hikaru Ichijyo <ichijyo@macross.sdf.jp>
To: info-gnus-english@gnu.org
Subject: Re: moving articles from mail groups
Date: Sun, 24 May 2015 02:47:07 -0500 [thread overview]
Message-ID: <8xxfv6mfmdg.fsf@village.keycorner.org> (raw)
In-Reply-To: <87y4keyhd6.fsf@debian.uxu>
Emanuel Berg <embe8573@student.uu.se> writes:
> Hikaru Ichijyo <ichijyo@macross.sdf.jp> writes:
>> With that setup, when I use
>> gnus-summary-move-article (B m) to move an article
>> from my mail groups into one of these nnfolder
>> files, I get prompted like this:
>>
>> Move this article to (default
>> nnfolder:freenet): nnmbox:
>>
>> Yes, that "nnmbox:" part gets printed by the system
>> (not by me).
>
> Why do you want to store the messages using
> another backend?
The manual uses nnfolder as an example of how a user may keep an archive
of mailboxes all in a subdirectory for mail they may keep. I couldn't
see anything wrong with the idea. In fact, the syntax for how I've done
this is mostly taken from the manual.
> And why do you want to do this manually by hitting
> `B-m' each time? If you are fine with that, why are
> you not fine with hitting M-DEL each time as well?
>
> Better to automatize. For example, you can send a copy
> of all messages sent to yourself, then split it to
> archive folders based on header data.
This is not for saving *every* message. This is only for saving
particular messages I come across that I want to save. Because it is
only me deciding which messages those should be, it has to be manual.
Do you know why it's double-prompting me this way, or how to stop it?
--
He that would make his own liberty secure must guard even his enemy from
oppression; for if he violates this duty, he establishes a precedent
that will reach to himself.
--Thomas Paine
next prev parent reply other threads:[~2015-05-24 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 18:03 Hikaru Ichijyo
2015-05-24 0:00 ` Emanuel Berg
2015-05-24 7:47 ` Hikaru Ichijyo [this message]
2015-05-24 20:08 ` Emanuel Berg
2015-05-24 23:11 ` Emanuel Berg
2015-05-24 12:34 ` Dan Christensen
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=8xxfv6mfmdg.fsf@village.keycorner.org \
--to=ichijyo@macross.sdf.jp \
--cc=info-gnus-english@gnu.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).