From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56796@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#56796: 29.0.50; Hard newlines not respected in code comments?
Date: Fri, 29 Jul 2022 10:32:21 -0400 [thread overview]
Message-ID: <jwv1qu49eop.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83k07xaea1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2022 10:26:46 +0300")
> Adding Stefan to CC, who write fill-comment-paragraph. If we want
> use-hard-newlines to be supported in comments, we should modify
> fill-comment-paragraph to honor it in some way, perhaps simply
> deferring to fill-region in that case.
It was many years ago, but IIRC the autor of that code presumed it was
used in "code" and he also presumed that hard newlines are only for
"text", and furthermore it presumed that the two are mutually exclusive.
He was apparently a quite naive young fellow,
At the same time, I'm not sure how important it is to handle hard
newlines in ELisp comments, so I'm not sure how important it is to
fix this. This bug report only gives a (good) recipe but not a good
reason for doing such a thing, so maybe some context explaining how/why
such hard newlines can appear in comments would help motivate a fix.
Stefan
next prev parent reply other threads:[~2022-07-29 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:49 bug#56796: 29.0.50; Hard newlines not respected in code comments? Visuwesh
2022-07-28 7:26 ` Eli Zaretskii
2022-07-28 8:20 ` Visuwesh
2022-07-29 14:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-29 14:55 ` Visuwesh
2022-07-29 15:02 ` Visuwesh
2022-07-29 15:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-29 16:16 ` Visuwesh
2022-07-29 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwv1qu49eop.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=56796@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=visuweshm@gmail.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).