From: Dmitry Gutov <dmitry@gutov.dev>
To: Ankit Gadiya <ankit@argp.in>, 69562@debbugs.gnu.org
Subject: bug#69562: 29.2.50; go-ts-mode does not handle comments with fill-paragraph
Date: Thu, 7 Mar 2024 03:57:14 +0200 [thread overview]
Message-ID: <3eeffc6b-edd7-462b-a7da-d3463c08ca5f@gutov.dev> (raw)
In-Reply-To: <CAN7zea2EcB0b61Ctkr=da_T7y=y6tb+7S4YMM8ojLhLA6=UfAQ@mail.gmail.com>
On 06/03/2024 07:22, Ankit Gadiya wrote:
>> Are you testing in the same Emacs as the one you filed the bug report in?
>>
>
> Yes, I only have one Emacs version installed on my system and I'm currently
> tracking the emacs-29 branch (last compiled maybe a week ago). I tried enabling
> `debug-on-entry` for the `fill-paragraph` function. Here is the
> Backtrace if it's
> useful. I think beyond this it goes into lower level buffer manipulation
> functions.
>
>
> current-left-margin()
> * move-to-left-margin()
> * forward-paragraph(1)
> * fill-forward-paragraph(1)
> * fill-region(17 269 nil)
Sorry, I'm not noticing anything odd here.
>>> Today @stebalien@emacs.ch suggested to set adaptive-fill-regexp for go-ts-mode
>>> and that solved it for me (if this is useful).
>>>
>>> (setq-mode-local go-ts-mode adaptive-fill-regexp "[ \t]*//+[ \t]*")
>>
>> TBH I'm not yet sure what the value of this variable should look like.
>> But if I manage to reproduce the bug on my machine, this will be the
>> next thing we can try, thanks.
>
> I also tried pulling the latest grammar for go and it's still
> reproducing on my machine.
Could you confirm that your problem reproduces if you start Emacs as
'emacs -Q'?
next prev parent reply other threads:[~2024-03-07 1:57 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3eeffc6b-edd7-462b-a7da-d3463c08ca5f@gutov.dev \
--to=dmitry@gutov.dev \
--cc=69562@debbugs.gnu.org \
--cc=ankit@argp.in \
/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.