From: Yuan Fu <casouri@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 62238@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>,
theodor thornhill <theo@thornhill.no>
Subject: bug#62238: 30.0.50; Unusual interpretation of "S-expressions" in c-ts-mode
Date: Sat, 18 Mar 2023 14:34:03 -0700 [thread overview]
Message-ID: <489C4C6A-D7E5-4EC6-8C1E-237F1AE581EF@gmail.com> (raw)
In-Reply-To: <87edpmuz9p.fsf@gmail.com>
> On Mar 18, 2023, at 3:31 AM, Kévin Le Gouguec <kevin.legouguec@gmail.com> 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.
Duh, ok, I know what’s going on. Theo added some sexp related tree-sitter stuff to master, but I’ve been focusing on emacs-29. On emacs-29, c-ts-mode doesn’t redefine forward-sexp-function and the default function uses the syntax table, which works fine.
Yuan
prev parent reply other threads:[~2023-03-18 21:34 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
2023-03-18 21:34 ` Yuan Fu [this message]
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=489C4C6A-D7E5-4EC6-8C1E-237F1AE581EF@gmail.com \
--to=casouri@gmail.com \
--cc=62238@debbugs.gnu.org \
--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 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.