From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 56796@debbugs.gnu.org
Subject: bug#56796: 29.0.50; Hard newlines not respected in code comments?
Date: Thu, 28 Jul 2022 13:50:06 +0530 [thread overview]
Message-ID: <87pmhpodhl.fsf@gmail.com> (raw)
In-Reply-To: <83k07xaea1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2022 10:26:46 +0300")
[வியாழன் ஜூலை 28, 2022] Eli Zaretskii wrote:
>> From: Visuwesh <visuweshm@gmail.com>
>> Date: Wed, 27 Jul 2022 21:19:29 +0530
>>
>> Are hard newlines supposed to be respected when they are in code
>> comments?
>
> The answer is "it depends", AFAICS.
>
> The main problem is that fill-comment-paragraph doesn't seem to honor
> use-hard-newlines. So any major mode whose fill-paragraph-function
> uses that for filling comments will fail to pay attention to hard
> newlines in comments. In your scenario, if I set both
> fill-paragraph-function and fill-paragraph-handle-comment to nil, hard
> newlines in comments are honored as expected.
Thanks for the explanation, I figured that was the case.
> 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.
That would be most welcome. Hard newlines was the "missing key" in
making writing plain text more easy and enjoyable to me.
next prev parent reply other threads:[~2022-07-28 8:20 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 [this message]
2022-07-29 14:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmhpodhl.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=56796@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.