From: Florian von Savigny <florian265@uboot.com>
Subject: Re: modifying movemail
Date: 20 Jun 2004 00:45:43 +0200 [thread overview]
Message-ID: <m3r7sb5fqg.fsf@uboot.com> (raw)
In-Reply-To: 87wu236vxe.fsf@thalassa.informatimago.com
We both seem to be online right now, the way you were faster than my
immediate addendum...
Pascal Bourguignon <spam@thalassa.informatimago.com> writes:
> > So thanks a lot - but is anybody able to help with the conversion (or
> > supply a pointer to the right information)?
>
>
> In emacs: C-h i m emacs RET m rmail RET m movemail RET
Sorry, I thought I had already read this information and that it
contained nothing helpful. That wasn't quite right:
--snip--
When getting new mail, Rmail first copies the new mail from the inbox
file to the Rmail file; then it saves the Rmail file; then it truncates
the inbox file. This way, a system crash may cause duplication of mail
between the inbox and the Rmail file, but cannot lose mail.
--snap--
Thus, normally, movemail isn't even used. That had escaped me.
--snip--
In some cases, Rmail copies the new mail from the inbox file
indirectly. First it runs the `movemail' program to move the mail from
the inbox to an intermediate file called `~/.newmail-INBOXNAME'. Then
Rmail merges the new mail from that file, saves the Rmail file, and
only then deletes the intermediate file.
--snap--
Sounds like this intermediate file is the second argument to movemail.
What makes me wonder now is: is the fact alone that emacs under Linux
hangs when trying to rmail-get-new-mail from a spool file on a FAT32
partition enough proof that it is using movemail? After all, it might
hang when executing its lisp code, and modifying movemail would not
change a bit about that...
[I'll spare the theoretical question: under what circumstances and why
Emacs (does not) use(s) movemail.]
--
Florian v. Savigny
If you are going to reply in private, please be patient, as I only
check for mail something like once a week. - Si vous allez répondre
personellement, patientez s.v.p., car je ne lis les courriels
qu'environ une fois par semaine.
next prev parent reply other threads:[~2004-06-19 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 10:27 modifying movemail Florian von Savigny
2004-06-19 17:39 ` Pascal Bourguignon
2004-06-19 21:54 ` Florian von Savigny
2004-06-19 22:10 ` Pascal Bourguignon
2004-06-19 22:45 ` Florian von Savigny [this message]
2004-06-20 5:32 ` Pascal Bourguignon
2004-06-19 22:28 ` Florian von Savigny
2004-06-20 5:42 ` Pascal Bourguignon
2004-06-20 10:13 ` Florian von Savigny
2004-06-20 10:46 ` poor man's movemail Florian von Savigny
2004-06-21 13:26 ` modifying movemail Thien-Thi Nguyen
2004-07-01 10:17 ` Kai Grossjohann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r7sb5fqg.fsf@uboot.com \
--to=florian265@uboot.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).