unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: 56796@debbugs.gnu.org
Cc: eliz@gnu.org, monnier@iro.umontreal.ca
Subject: bug#56796: 29.0.50; Hard newlines not respected in code comments?
Date: Fri, 29 Jul 2022 20:25:14 +0530	[thread overview]
Message-ID: <87fsikynn1.fsf@gmail.com> (raw)
In-Reply-To: <jwv1qu49eop.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Fri, 29 Jul 2022 10:32:21 -0400")

[வெள்ளி ஜூலை 29, 2022] Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:

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

Well, wrt Elisp comments at least, we have the Commentary section where
we write quite a lot about the package in question where having hard
newlines would be really handy since you write those text like you do in
a regular text buffer.

More generally: I'm not sure how common this pattern is but I tend to do

    ;; TODO/FIXME: Something...
    ;; Ideas and thoughts on how to clear it here.

Now if you do M-q there, your neatly arranged text is destroyed.  (I am
probably biased) I also catch this pattern in the Emacs source tree as
well.

[ Although not related to Elisp: Documentation for functions/whatever in
  Go are written as comments.  ]





  reply	other threads:[~2022-07-29 14:55 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
2022-07-29 14:55     ` Visuwesh [this message]
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=87fsikynn1.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 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).