From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
60525@debbugs.gnu.org, larsi@gnus.org, dgutov@yandex.ru
Subject: bug#60525: 29.0.60; tree-sitter support in semantic-symref
Date: Thu, 05 Jan 2023 19:29:35 +0200 [thread overview]
Message-ID: <86mt6x73wo.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwv4jt6dv0i.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 04 Jan 2023 13:20:26 -0500")
>>>> >> On 03/01/2023 20:06, Juri Linkov wrote:
>>>> >> > + (c-ts-mode "*.[ch]")
>>>> >> > (c++-mode "*.[chCH]" "*.[ch]pp" "*.cc" "*.hh")
>>>> >> > + (c++-ts-mode "*.[chCH]" "*.[ch]pp" "*.cc" "*.hh")
>>>> >> > (html-mode "*.html" "*.shtml" "*.php")
>>>> >> > (mhtml-mode "*.html" "*.shtml" "*.php") ; FIXME: remove
>>>> >> > ; duplication of
>>>> >> > @@ -53,7 +55,10 @@ semantic-symref-filepattern-alist
>>>> >> > ; major mode definition?
>>>> >> > (ruby-mode "*.r[bu]" "*.rake" "*.gemspec" "*.erb" "*.haml"
>>>> >> > "Rakefile" "Thorfile" "Capfile" "Guardfile" "Vagrantfile")
>>>> >> > + (ruby-ts-mode "*.r[bu]" "*.rake" "*.gemspec" "*.erb" "*.haml"
>>>> >> > + "Rakefile" "Thorfile" "Capfile" "Guardfile" "Vagrantfile")
>>>> >> > (python-mode "*.py" "*.pyi" "*.pyw")
>
> BTW, I see that the info provided by `semantic-symref-filepattern-alist`
> could be (re)used also in `C-u M-x grep`.
Indeed, another duplication with:
(defcustom grep-files-aliases
'(("all" . "* .*")
("el" . "*.el")
("ch" . "*.[ch]")
("c" . "*.c")
("cc" . "*.cc *.cxx *.cpp *.C *.CC *.c++")
("cchh" . "*.cc *.[ch]xx *.[ch]pp *.[CHh] *.CC *.HH *.[ch]++")
("hh" . "*.hxx *.hpp *.[Hh] *.HH *.h++")
("h" . "*.h")
("l" . "[Cc]hange[Ll]og*")
("am" . "Makefile.am GNUmakefile *.mk")
("m" . "[Mm]akefile*")
("tex" . "*.tex")
("texi" . "*.texi")
("asm" . "*.[sS]"))
next prev parent reply other threads:[~2023-01-05 17:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 18:06 bug#60525: 29.0.60; tree-sitter support in semantic-symref Juri Linkov
2023-01-03 20:19 ` Eli Zaretskii
2023-01-04 1:51 ` Dmitry Gutov
2023-01-04 7:43 ` Juri Linkov
2023-01-04 12:06 ` Dmitry Gutov
2023-01-04 14:34 ` Eli Zaretskii
2023-01-04 14:26 ` Eli Zaretskii
2023-01-04 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 16:57 ` Eli Zaretskii
2023-01-04 17:03 ` Dmitry Gutov
2023-01-04 17:17 ` Eli Zaretskii
2023-01-04 18:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 18:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 18:43 ` Eli Zaretskii
2023-01-04 19:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05 17:29 ` Juri Linkov [this message]
2023-01-04 18:39 ` Eli Zaretskii
2023-01-04 19:04 ` Dmitry Gutov
2023-01-04 19:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05 18:18 ` Juri Linkov
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=86mt6x73wo.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=60525@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).