From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: eliz@gnu.org
Cc: casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-29 fb5d9ff559 1/2: Fix c-ts-mode defun movement (bug#59628)
Date: Fri, 2 Dec 2022 07:30:44 +0100 [thread overview]
Message-ID: <4c9cb97a-f792-0c2e-bb29-3fa631d34225@gmail.com> (raw)
In-Reply-To: <83zgc7gmz1.fsf@gnu.org>
>> ;; Navigation.
>> (setq-local treesit-defun-type-regexp
>> - (rx (or "specifier"
>> - "definition")))
>> + (rx (or "function_definition"
>> + "type_definition"
>> + "struct_specifier"
>> + "enum_specifier"
>> + "union_specifier")))
>
> Shouldn't we use regex-opt here?
The or-clause of rx does that already.
next prev parent reply other threads:[~2022-12-02 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 15:30 emacs-29 fb5d9ff559 1/2: Fix c-ts-mode defun movement (bug#59628) Eli Zaretskii
2022-12-02 2:53 ` Yuan Fu
2022-12-02 6:30 ` Gerd Möllmann [this message]
2022-12-02 8:39 ` Eli Zaretskii
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=4c9cb97a-f792-0c2e-bb29-3fa631d34225@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).