unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Harig <idirectscm@aim.com>
Cc: 58145@debbugs.gnu.org
Subject: bug#58145: Formatting of lines in this report.
Date: Thu, 29 Sep 2022 09:08:43 +0300	[thread overview]
Message-ID: <83pmfehfv8.fsf@gnu.org> (raw)
In-Reply-To: <113300612.1180976.1664409726415@mail.yahoo.com> (bug-gnu-emacs@gnu.org)

> Date: Thu, 29 Sep 2022 00:02:06 +0000 (UTC)
> From:  Mark Harig via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> The display of this report at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58145 appears to omit many
> newline characters that were in the original mail/report.  Is this expected, or is there something that can be
> done to prevent this?  (Thank you for any help that can prevent this in future reports.)
> 
> The original formatting (more readable) of the report can be seen by clicking on the "Message part 2" link at
> the bottom of https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58145.

Your message included a text/plain part (which was in quoted-printable
encoding), and a text/html part.  The latter displays as you'd like,
but the former is what you see on debbugs.  The reason is that the MUA
you are using produces strange EOL sequences, which have no indication
of a newline: NBSP SPC NBSP.  You can clearly see that if you click
the "mbox" link on the message header line, which leads to this:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58145;mbox=yes;msg=5

Download the mbox file and examine it, and you will see what I
describe above.

So I think the problem is with the configuration of your MUA.





  reply	other threads:[~2022-09-29  6:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1167367840.1034373.1664378697992.ref@mail.yahoo.com>
2022-09-28 15:24 ` bug#58145: 28.1; Description errors in Emacs's info manual for Gnus key bindings Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29  0:02   ` bug#58145: Formatting of lines in this report Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29  6:08     ` Eli Zaretskii [this message]
2022-09-29 11:05   ` bug#58145: 28.1; Description errors in Emacs's info manual for Gnus key bindings 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=83pmfehfv8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58145@debbugs.gnu.org \
    --cc=idirectscm@aim.com \
    /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).