>> How does a "mailbox" differ from something that
>> is NOT one?
>Any mailbox file can be treated like a text file
>but not vice versa. The mails contained are
>separated by a delimiter. Look at the first line
>of the file and discover the magic "From " line.
As far as I can tell, this fact isn't documented
anywhere. Thanks for the needed info!
>> Until I edited the "mailbox file", and inserted
>> some messages that had wrongly gotten saved into
>> a mailbox I didn't want them in, "s" worked fine.
>Next time you'd better change into the other mailbox
>from within mutt and save the messages again into the
>correct mailbox. Let mutt do this for you :-)
(1) "better change into the other mailbox":
This is a big part of what I do not understand,
having experience with *only* unix/sun "mail"
and now mutt:
. What *is* a "folder"? (a file? a directory? what?)
. What is *special* about a "folder"?
. What is a "mailbox"? Same as "folder"?
. What does it mean to "switch from one
mailbox to another"?
--- ALSO: about "and save the message again":
. but by the time I *realized* that the msg
had gone to the wrong "=<filename>", I had
*already deleted* the message from mutt.
Given that, how to move a message from
one =file to another?
.. via mutt?
.. via vi, vim, emacs, ...
>> PS: what effect does the prefix "=" have on
>> a file to save an email into?
>It's a shortcut for the pathname where your mailboxes
>are stored into. Like "~/Mail" for most people.
That too seems to be undocumented -- thank you
VERY much for that info, too.
>> > Mindestens drei Leute, zwei Meinungen, und Recht hat RFC 2046, 4.1.2.
>> RFC 2046 enth?lt genug Seil, um sich in den Fu? zu schie?en.
> [Gunnar Ritter und Claus F?rber in de.comp.standards, 2001-04-10]
You probably know who updates the mutt documentation;
perhaps you could forward this on to them, so
it can be updated to include all this stuff, or
if already there, made "louder".