From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 64487@debbugs.gnu.org
Subject: bug#64487: 29.0.92; Another tree-sitter warning inside Custom
Date: Tue, 27 Feb 2024 06:23:36 +0200 [thread overview]
Message-ID: <d0824f9d-0bf8-4d62-9532-54861c2e384f@gutov.dev> (raw)
In-Reply-To: <86edczupjg.fsf@gnu.org>
On 26/02/2024 19:02, Eli Zaretskii wrote:
>> Date: Mon, 26 Feb 2024 18:55:09 +0200
>> Cc:luangruo@yahoo.com,64487@debbugs.gnu.org
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>> I remember you saying that it was a question which is settled until any
>> other problems come up. Isn't this an example of such problem?
> No, I don't think so. It is a very special case, which is rarely a
> problem (only if the user decides eventually not to activate the
> mode).
Which mode, though?
The sequence of actions does not pertain to any particular mode: it's
just Customize -> Programming -> Languages.
Going through these steps with 'emacs -Q' here, I got both a warning
about the missing lua grammar (14 lines tall), and both ruby-ts-mode and
elixir-ts-mode added to auto-mode-alist, which weren't there before.
And then visiting the "C" node (which is not specific to the tree-sitter
modes, to be clear -- it's mostly CC Mode variables), I get also
c-ts-mode, c++-ts-mode and c-or-c++-ts-mode added there.
There would be more modes added, but apparently some use groups with no
parent defined (such as 'java' or 'json'), so they're not reachable from
the general Customize interface.
next prev parent reply other threads:[~2024-02-27 4:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871qhlmssz.fsf.ref@yahoo.com>
2023-07-06 6:56 ` bug#64487: 29.0.92; Another tree-sitter warning inside Custom Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-06 9:12 ` Eli Zaretskii
2024-02-26 11:13 ` Morgan Willcock
2024-02-26 16:25 ` Dmitry Gutov
2024-02-26 16:49 ` Eli Zaretskii
2024-02-26 16:55 ` Dmitry Gutov
2024-02-26 17:02 ` Eli Zaretskii
2024-02-27 4:23 ` Dmitry Gutov [this message]
2024-02-27 8:11 ` 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=d0824f9d-0bf8-4d62-9532-54861c2e384f@gutov.dev \
--to=dmitry@gutov.dev \
--cc=64487@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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).