From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ken Olum <kdo@cosmos.phy.tufts.edu>
Cc: 39580@debbugs.gnu.org
Subject: bug#39580: 26.2; missing newline in fcc when output file is in an rmail buffer
Date: Tue, 27 Oct 2020 19:14:27 +0100 [thread overview]
Message-ID: <87o8kn1qpo.fsf@gnus.org> (raw)
In-Reply-To: <q52pnejodcv.fsf@cosmos.phy.tufts.edu> (Ken Olum's message of "Wed, 12 Feb 2020 13:43:44 -0500")
Ken Olum <kdo@cosmos.phy.tufts.edu> writes:
> The function gnus-output-to-rmail fails to ensure a blank line at the
> end of the message being output in the case where the output file is an
> mbox file viewed in an rmail buffer. The needed code is in this
> function, but triggers only when the output file is not in a buffer.
> This causes messages in the output file to be merged together.
>
> To reproduce:
>
> emacs -Q
> C-x m to compose message
> edit outgoing message to add a line "Fcc: test-save" (for example) and
> some body that does not have a blank line at the end.
> C-c C-c to send message
> Visit "test-save"
> M-x rmail-mode
> Select buffer "*sent mail to ...*"
> C-c C-c to send message again
>
> File "test-save" is now corrupt because it lacks a blank line at the
> end.
I'm able to reproduce this bug, but I'm not sure how
gnus-output-to-rmail is involved here? As far as I can see, it's never
called by Message, and instead `message-output' is called to create the
file.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-27 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 18:43 bug#39580: 26.2; missing newline in fcc when output file is in an rmail buffer Ken Olum
2020-10-27 18:14 ` Lars Ingebrigtsen [this message]
2020-10-27 18:16 ` Lars Ingebrigtsen
2020-10-27 18:29 ` Lars Ingebrigtsen
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=87o8kn1qpo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39580@debbugs.gnu.org \
--cc=kdo@cosmos.phy.tufts.edu \
/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).