[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#39580: 26.2; missing newline in fcc when output file is in an rmail
bug#39580: 26.2; missing newline in fcc when output file is in an rmail buffer
Wed, 12 Feb 2020 13:43:44 -0500
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.
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
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. To see that it is corrupt:
Send the same message yet again.
Select the "test-save" buffer. It will look OK, but
Kill the "test-save" buffer.
Visit "test-save" again
Now the last two copies of the message will be concatenated into a
I propose fixing this by taking the code for inserting the blank line
that starts "(unless babyl ; from gnus-output-to-mail" and moving it
before ";; Decide whether to append to a file or to an Emacs buffer." so
that it takes place for all mbox files.
There is a similar bug in gnus-output-to-mail that occurs when the file
is in a non-rmail buffer. It makes the same mistake, but corrects it
next time by putting in another newline at the end of what it did
before. However, it always adds the newline, so if the file is empty it
corrupts it by putting an extra blank line at the front.
|[Prev in Thread]
||[Next in Thread]|
- bug#39580: 26.2; missing newline in fcc when output file is in an rmail buffer,
Ken Olum <=