unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Lillibridge <mdl@alum.mit.edu>
To: Eli Zaretskii <eliz@gnu.org>
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, 10 Oct 2022 10:17:08 -0700	[thread overview]
Message-ID: <87czazlht7.fsf@alum.mit.edu> (raw)
In-Reply-To: <83illalgp1.fsf@gnu.org> (message from Eli Zaretskii on Mon, 26 Sep 2022 03:48:21 -0400)


Eli Zaretskii <eliz@gnu.org> writes:

>  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.

    I agree this is not a particularly urgent/important bug.  If there
are more important bugs to fix and we have limited fixer bandwidth, I
don't think it would be unreasonable to mark this as "won't fix" or the
like.  I reopened this mostly because it was closed with the state
"fixed/gone", which is incorrect.

- Mark





      parent reply	other threads:[~2022-10-10 17:17 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
2022-09-26 10:53     ` Lars Ingebrigtsen
2022-10-10 17:17     ` Mark Lillibridge [this message]

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