unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mdl@alum.mit.edu
Cc: larsi@gnus.org, 10080@debbugs.gnu.org
Subject: bug#10080: 23.3; Rmail shows an extra blank line at the end when displaying a non-MIME message
Date: Mon, 26 Sep 2022 10:48:10 +0300	[thread overview]
Message-ID: <83illalgp1.fsf@gnu.org> (raw)
In-Reply-To: <87a66nbed0.fsf@alum.mit.edu> (message from Mark Lillibridge on Sun, 25 Sep 2022 09:36:27 -0700)

> From: Mark Lillibridge <mdl@alum.mit.edu>
> Date: Sun, 25 Sep 2022 09:36:27 -0700
> 
>     I'm attaching a *mbox* file (this is the format used by rmail),
> lightly edited from one of my older rmail files to hide email addresses.
> It has two messages, the first with zero blank lines at the end and last
> with 2 blank lines at the end.  If you find file it then do M-x
> rmail-mode and look at the first message, you will see that it has an
> extra blank line at the end when displayed.  The last one doesn't.  (go
> to the end of message with esc > or turn on line numbering to see where
> the displayed message ends.)
> 
>     If you look at the rmail file before doing rmail-mode, you can see
> the underlying formatting.  You will see a blank line between the first
> and second message; this is part of the mbox formatting, not a part of
> either message.
> 
> from https://en.wikipedia.org/wiki/Mbox
>     The mbox format uses a single blank line followed by the string 'From '
>     (with a space) to delimit messages; this can create ambiguities if a
>     message contains the same sequence in the message text.
> 
> (The original reproduction instructions probably no longer work because
> it's actually quite hard to send a message that's not using MIME these
> days.)
> 
>     To add insult to injury, if you attempt to forward the message, Rmail
> will include the spurious blank line in the message it forwards.  I hit
> 'f' for this in emacs28.1 -q and get a # part with the blank line before
> the closing tag.

Can you explain why this is a problem?  That is, why does it matter
that a message, as shown in the Rmail reading buffer, has extra empty
lines at the end?  I use Rmail all the time, and know about these
extra empty lines, but they never bother me, because I don't need to
read empty lines.  And forwarding a message with an extra empty line
also should not cause any trouble on the receiving end.

So I'm not sure we should do anything with this bug.





  reply	other threads:[~2022-09-26  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19 22:00 bug#10080: 23.3; Rmail shows an extra blank line at the end when displaying a non-MIME message Mark Lillibridge
2021-06-02  7:43 ` Lars Ingebrigtsen
2021-06-30 13:22   ` Lars Ingebrigtsen
2022-09-25 16:36 ` Mark Lillibridge
2022-09-26  7:48   ` Eli Zaretskii [this message]
2022-09-26 10:53     ` Lars Ingebrigtsen
2022-10-10 17:17     ` Mark Lillibridge

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=83illalgp1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=10080@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mdl@alum.mit.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).