From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs 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 Message-ID: <83illalgp1.fsf@gnu.org> References: <8762ifeps3.fsf@hp.com> <87a66nbed0.fsf@alum.mit.edu> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28873"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 10080@debbugs.gnu.org To: mdl@alum.mit.edu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 26 09:49:24 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ocirk-0007Nv-Dp for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 26 Sep 2022 09:49:24 +0200 Original-Received: from localhost ([::1]:37816 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ocirh-0000TD-Fs for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 26 Sep 2022 03:49:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47638) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ocirO-0000NU-Lo for bug-gnu-emacs@gnu.org; Mon, 26 Sep 2022 03:49:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50107) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ocirO-0000oi-BF for bug-gnu-emacs@gnu.org; Mon, 26 Sep 2022 03:49:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ocirN-0000S6-W8 for bug-gnu-emacs@gnu.org; Mon, 26 Sep 2022 03:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 26 Sep 2022 07:49:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 10080 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 10080-submit@debbugs.gnu.org id=B10080.16641785081689 (code B ref 10080); Mon, 26 Sep 2022 07:49:01 +0000 Original-Received: (at 10080) by debbugs.gnu.org; 26 Sep 2022 07:48:28 +0000 Original-Received: from localhost ([127.0.0.1]:49183 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ociqq-0000RB-Ce for submit@debbugs.gnu.org; Mon, 26 Sep 2022 03:48:28 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33748) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ociqp-0000Qw-5E for 10080@debbugs.gnu.org; Mon, 26 Sep 2022 03:48:27 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59258) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ociqj-0000kV-4c; Mon, 26 Sep 2022 03:48:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=8LHNO3TUyd1FWUXM45cJFCpLocZiF+EQW8f6euSaQ0w=; b=kUXokAL1yynv Q5cm770q0f8wCN8JwoxxS0AC79MH3mJSgs47UkwC5pOd3VWROqH2Yz+eBea4yqdRwajXHophLN/OO YebQcOGMi5FeHtFmIN+dpLfjRvHBQCoPYwE6Dnp0cu7FTX+ZDxV13qHfDDSWs7JDIOkW26mhhn50O J44610T7nS08l9+QvtZ0KNN74aGv7WZoEGz+bJyBmVFsdCOFwwL6WB/6ZTBO4P1amg9EmD/0La/Yj zBmMFN+e3XF0hlx+MfQ4xq2hP1ehrUmvrQvWRqmdc914LLeueLMlGvjWwioaycaJulcA+QSaK8NRy VTTlmt3MTBX852fhy8Mf2Q==; Original-Received: from [87.69.77.57] (port=2042 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ociqi-0000Ef-Jr; Mon, 26 Sep 2022 03:48:20 -0400 In-Reply-To: <87a66nbed0.fsf@alum.mit.edu> (message from Mark Lillibridge on Sun, 25 Sep 2022 09:36:27 -0700) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:243624 Archived-At: > From: Mark Lillibridge > 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.