From: Eli Zaretskii <eliz@gnu.org>
To: emacs-bug@rulnick.com
Cc: 65071@debbugs.gnu.org
Subject: bug#65071: 29.1; RMAIL changed on disk leads to rmail-error-bad-format
Date: Sun, 06 Aug 2023 09:36:45 +0300 [thread overview]
Message-ID: <83fs4wr81u.fsf@gnu.org> (raw)
In-Reply-To: <m2sf8xicr7.fsf@rulnick.com> (emacs-bug@rulnick.com)
> From: emacs-bug@rulnick.com
> Cc: 65071@debbugs.gnu.org
> Date: Sat, 05 Aug 2023 14:07:40 -0400
>
> I hope the receipe below is clearer. In Emacs 29.1, starting with no
> ~/RMAIL file and empty primary mail spool file (please note that '$'
> indicates Bash prompt in Terminal independent of Emacs):
>
> $ mail me@foo ... # send a message to myself
>
> $ emacs -Q
>
> (in Emacs) M-x rmail RET # retrieves/reads message
>
> $ cat /dev/null > ~/RMAIL # clear RMAIL file
>
> $ mail me@foo ... # send another message to myself
>
> (in Emacs) g
>
> "File RMAIL changed on disk. Reread from disk? (yes or no) " yes RET
>
> "rmail-error-bad-format: Message is not a valid RFC 822 (or later)
> message"; Emacs mode changes from RMAIL to Fundamental
>
> At this point the ~/RMAIL file on disk looks good (proper RFC 822 file),
> but the ~/RMAIL file as visited in buffer looks bad, as can be seen
> (e.g., upon immediate save) to be missing top "From " and other header
> lines ("Return-Path:", "Received:", etc.). I have many years experience
> with Emacs and RMAIL and this behavior is new as of 29.1 or another very
> recent version of Emacs.
Thanks, this should be fixed now on the emacs-29 branch. The reason
for the bug was a change in revert-buffer we made during Emacs 29
development.
next prev parent reply other threads:[~2023-08-06 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 18:18 bug#65071: 29.1; RMAIL changed on disk leads to rmail-error-bad-format emacs-bug
2023-08-05 10:00 ` Eli Zaretskii
2023-08-05 10:31 ` emacs-bug
2023-08-05 10:52 ` Eli Zaretskii
2023-08-05 18:07 ` emacs-bug
2023-08-06 6:36 ` Eli Zaretskii [this message]
2023-08-12 6:52 ` Eli Zaretskii
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=83fs4wr81u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65071@debbugs.gnu.org \
--cc=emacs-bug@rulnick.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).