From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: ankit@argp.in, 69562@debbugs.gnu.org
Subject: bug#69562: 29.2.50; go-ts-mode does not handle comments with fill-paragraph
Date: Tue, 05 Mar 2024 17:49:09 +0200 [thread overview]
Message-ID: <86o7bsllvu.fsf@gnu.org> (raw)
In-Reply-To: <9078f92b-f567-42ce-8539-30eb7d097828@gutov.dev> (message from Dmitry Gutov on Tue, 5 Mar 2024 16:49:44 +0200)
> Cc: 69562@debbugs.gnu.org
> Date: Tue, 5 Mar 2024 16:49:44 +0200
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 05/03/2024 16:22, Ankit Gadiya wrote:
> >> Does you example originally have one long commented line? Because when I
> >> try it that way, filling seems to work fine, comments are added on the
> >> new lines.
> >
> > Yes, I think the lines got wrapped in the mail but I had a long line. Admittedly
> > that sample is specifically to showcase the issue but a more realistic scenario
> > is when I already have multiline comments, I update it and want to re-fill
> > it. Here also, it is clear that fill-paragraph does not respect the comment
> > delimiter so it moves them just like regular characters.
> >
> > (all comment lines start with // in case mail adds line breaks)
> >
> > // Sample is a sample function with a very long comment. Sample is a
> > // new details added to the comment sample function with a very
> > long comment. Sample is a sample function
> > // with a very long comment. Sample is a sample function with a very long
> > // comment.
> > func Sample() {
> >
> > }
> >
> > Becomes this
> >
> > // Sample is a sample function with a very long comment. Sample is a // new
> > details added to the comment sample function with a very long
> > comment. Sample is
> > a sample function // with a very long comment. Sample is a sample
> > function with
> > a very long // comment.
> > func Sample() {
> >
> > }
>
> That's odd: here it becomes
>
> // Sample is a sample function with a very long comment. Sample is a
> // new details added to the comment sample function with a very long
> // comment. Sample is a sample function with a very long
> // comment. Sample is a sample function with a very long comment.
> func Sample() {
Could it be that you two use different versions of the grammar
library?
next prev parent reply other threads:[~2024-03-05 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 8:41 bug#69562: 29.2.50; go-ts-mode does not handle comments with fill-paragraph Ankit Gadiya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-05 12:44 ` Eli Zaretskii
2024-03-05 13:03 ` Dmitry Gutov
[not found] ` <CAN7zea2d+Ku3YG6hw9xw1xKRkkomf7pji8JArZskHbJ2CwZOGw@mail.gmail.com>
2024-03-05 14:49 ` Dmitry Gutov
2024-03-05 15:49 ` Eli Zaretskii [this message]
2024-03-05 18:59 ` Dmitry Gutov
2024-03-06 5:22 ` Ankit Gadiya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 1:57 ` Dmitry Gutov
2024-03-07 8:58 ` Ankit Gadiya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 9:38 ` Eli Zaretskii
2024-03-07 10:18 ` Ankit Gadiya via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CAN7zea13N9xgVLzQAFUiZiiVajB1vzQmh=vbaWOW97VKvL71Ww@mail.gmail.com>
2024-03-07 10:55 ` Eli Zaretskii
2024-03-07 11:13 ` Ankit Gadiya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 14:15 ` Dmitry Gutov
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=86o7bsllvu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69562@debbugs.gnu.org \
--cc=ankit@argp.in \
--cc=dmitry@gutov.dev \
/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).