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: Mon, 26 Feb 2024 18:55:09 +0200 [thread overview]
Message-ID: <544ebf3e-a11e-48e9-a380-33e3da52ab99@gutov.dev> (raw)
In-Reply-To: <86il2buq5h.fsf@gnu.org>
On 26/02/2024 18:49, Eli Zaretskii wrote:
>> Date: Mon, 26 Feb 2024 18:25:33 +0200
>> Cc: 64487@debbugs.gnu.org
>> From: Dmitry Gutov <dmitry@gutov.dev>
>>
>> On 06/07/2023 12:12, Eli Zaretskii wrote:
>>>> Date: Thu, 06 Jul 2023 14:56:44 +0800
>>>> From: Po Lu via "Bug reports for GNU Emacs,
>>>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>>>
>>>> Type M-x customize RET. Click Programming and then Languages. A
>>>> *Warnings* buffer will be displayed containing the following message:
>>>>
>>>> Warning (treesit): Cannot activate tree-sitter, because language
>>>> grammar for ruby is unavailable (not-found): (libtree-sitter-ruby
>>>> libtree-sitter-ruby.0 libtree-sitter-ruby.0.0 libtree-sitter-ruby.so
>>>> libtree-sitter-ruby.so.0 libtree-sitter-ruby.so.0.0) No such file or
>>>> directory
>>>
>>> When you customize a group, Custom loads all the packages that belong
>>> to the group. So in this case it loads ruby-ts-mode, and you get the
>>> warning.
>>
>> Which was never a problem before when simply loading a package didn't
>> alter auto-mode-alist.
>
> You want to start that old dispute again? I didn't expect you to
> change your opinions, and you shouldn't expect me to change mine. So
> why restart that?
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?
>> Do I understand it right that performing the simple steps that Po Lu
>> outlined would silently assign ruby-ts-mode to *.rb files? And a bunch
>> of other such modes that get loaded as well. But only until the end of
>> the session.
>
> Could be, I didn't try. If that's what happens, patches to avoid such
> a long-lasting effect, without changing what happens when the package
> is loaded outside of the Customize context, will be welcome.
I don't have any solutions to suggest except holding to the principle
that simply loading a package has as few side-effects as possible. Which
would mean reverting your earlier decision.
next prev parent reply other threads:[~2024-02-26 16:55 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 [this message]
2024-02-26 17:02 ` Eli Zaretskii
2024-02-27 4:23 ` Dmitry Gutov
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=544ebf3e-a11e-48e9-a380-33e3da52ab99@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).