From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Dmitry Gutov" <dgutov@yandex.ru>,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Yuan Fu" <casouri@gmail.com>
Cc: 62238@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: bug#62238: 30.0.50; Unusual interpretation of "S-expressions" in c-ts-mode
Date: Sat, 18 Mar 2023 19:00:16 +0100 [thread overview]
Message-ID: <81420033-8611-4BA2-A67B-E60631CE0331@thornhill.no> (raw)
In-Reply-To: <a16119c7-d1b6-a48d-1a35-f1ef0a6e7fe4@yandex.ru>
On 18 March 2023 18:48:10 CET, Dmitry Gutov <dgutov@yandex.ru> wrote:
>On 18/03/2023 12:31, Kévin Le Gouguec wrote:
>> Yuan Fu<casouri@gmail.com> writes:
>>
>>> I tested this on my Emacs session and vanilla session, and both marked to the
>>> closing bracket. I believe forward-sexp should just work by the syntax
>>> table. Perhaps it’s your config or something?
>> FWIW, I tested this on
>>
>> * the master branch (where Philip reported the bug): I can reproduce
>> Philip's results;
>>
>> 2023-03-18 "; * lisp/find-dired.el (find-gnu-find-p): Doc fix."
>> (95d5154feed)
>>
>> * emacs-29: things work as you (Yuan) describe.
>>
>> 2023-03-18 "; Fix 'make-obsolete-variable' forms" (faee8d50738)
>>
>> So maybe something that will get resolved by the next merge? Or
>> something that has been broken or master.
>
>Parse tree based forward-sexp was indeed only added on master.
>
Yeah
next prev parent reply other threads:[~2023-03-18 18:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 9:52 bug#62238: 30.0.50; Unusual interpretation of "S-expressions" in c-ts-mode Philip Kaludercic
2023-03-17 17:25 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 8:00 ` Yuan Fu
2023-03-18 10:29 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 12:11 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 13:32 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 13:33 ` Eli Zaretskii
2023-03-18 13:41 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 16:08 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 16:29 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 17:27 ` Eli Zaretskii
2023-03-19 17:28 ` Juri Linkov
2023-03-19 18:17 ` Eli Zaretskii
2023-03-20 18:13 ` Juri Linkov
2023-03-29 16:46 ` Juri Linkov
2023-03-18 10:31 ` Kévin Le Gouguec
2023-03-18 17:48 ` Dmitry Gutov
2023-03-18 18:00 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-03-18 21:34 ` Yuan Fu
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=81420033-8611-4BA2-A67B-E60631CE0331@thornhill.no \
--to=bug-gnu-emacs@gnu.org \
--cc=62238@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=dgutov@yandex.ru \
--cc=kevin.legouguec@gmail.com \
--cc=philipk@posteo.net \
--cc=theo@thornhill.no \
/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).