From: Frank Schmitt <usereplyto2004@Frank-Schmitt.net>
Subject: Re: The proper way to copy a message to another file...?
Date: Thu, 29 Jul 2004 08:58:54 +0200 [thread overview]
Message-ID: <m3llh3l2oh.fsf@fed1.frank-schmitt.net> (raw)
In-Reply-To: <upt6f1se9.fsf@tandika.com>
Steve Baker <steve@tandika.com> writes:
> On a solaris 9 box (if that makes any difference), I use nnfolders as
> my primary mail backend. I split out a few categories, but most of my
> mail ends up in a single file, where I read it. Once I read it, I may
> want to copy it to another file which is in the same nnfolders
> directory. I use gnus-summary-save-in-mail to do this.
I think it might work better if you use 'B c' to copy respectively 'B
m' to move the messages.
--
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.
parent reply other threads:[~2004-07-29 6:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <upt6f1se9.fsf@tandika.com>]
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=m3llh3l2oh.fsf@fed1.frank-schmitt.net \
--to=usereplyto2004@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).