GNU bug report logs - #72733
29.4; Warning message while attempting to view customization buffer

Previous Next

To reply to this bug, email your comments to 72733 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: tpeplt <tpeplt <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.4; Warning message while attempting to view customization buffer
Date: Tue, 20 Aug 2024 10:19:05 -0400

Emacs Maintainers,

   Emacs 29.4 appears to be running some (uninitialized?) code when a
sequence of sub-menus is selected.  This results in a warning message
about something that an Emacs user has not selected.  Here is a recipe
for reproducing the problem.  I have run this several times and gotten
the same result each time.

1. $ emacs -Q

2. M-x customize RET

3. The *Customize Group: Emacs* buffer is displayed.  In this buffer,
   select "Programming" from the menu of the Emacs group.

4. The *Customize Group: Programming* buffer is displayed.  In this
   buffer, select "Languages" from the menu.

5. A *Warnings* buffer is displayed in a new window.  The following
   warning message is displayed in that buffer:

⛔ 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

Please let me know if there is more information that you need to
reproduce this problem.

-- 

Message #8 received at 72733 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: tpeplt <tpeplt <at> gmail.com>
Cc: 72733 <at> debbugs.gnu.org
Subject: Re: bug#72733: 29.4;
 Warning message while attempting to view customization buffer
Date: Tue, 20 Aug 2024 17:32:51 +0300

> From: tpeplt <tpeplt <at> gmail.com>
> Date: Tue, 20 Aug 2024 10:19:05 -0400
> 
> Emacs Maintainers,
> 
>    Emacs 29.4 appears to be running some (uninitialized?) code when a
> sequence of sub-menus is selected.  This results in a warning message
> about something that an Emacs user has not selected.  Here is a recipe
> for reproducing the problem.  I have run this several times and gotten
> the same result each time.
> 
> 1. $ emacs -Q
> 
> 2. M-x customize RET
> 
> 3. The *Customize Group: Emacs* buffer is displayed.  In this buffer,
>    select "Programming" from the menu of the Emacs group.
> 
> 4. The *Customize Group: Programming* buffer is displayed.  In this
>    buffer, select "Languages" from the menu.
> 
> 5. A *Warnings* buffer is displayed in a new window.  The following
>    warning message is displayed in that buffer:
> 
> ⛔ 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

It's a known issue for which there's no simple solution.  We want
users who load ruby-ts-mode to know that they lack the Ruby grammar
library, which is what this warning is about.  And Customize loads
ruby-ts-mode to allow its customization when you select Languages.

We could perhaps shut up these specific warnings in that specific
situation, but that doesn't seem clean.  And the warning is just a
warning, and harmless.

Message #11 received at 72733 <at> debbugs.gnu.org (full text, mbox):

From: tpeplt <tpeplt <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 72733 <at> debbugs.gnu.org
Subject: Re: bug#72733: 29.4; Warning message while attempting to view
 customization buffer
Date: Tue, 20 Aug 2024 13:04:52 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>
> It's a known issue for which there's no simple solution.  We want
> users who load ruby-ts-mode to know that they lack the Ruby grammar
> library, which is what this warning is about.  And Customize loads
> ruby-ts-mode to allow its customization when you select Languages.
>
> We could perhaps shut up these specific warnings in that specific
> situation, but that doesn't seem clean.  And the warning is just a
> warning, and harmless.
>

It appears to be too minor a problem to add to the etc/PROBLEMS file
(C-h C-p).

If the maintainers agree that this is going to be a persistent problem,
then it might be worth adding a "Bugs" or "Known Bugs" section to the
Customization chapter of the Emacs user manual so that Emacs users can
read that this problem/behavior is known and not need to report it.
Maintainers would then be able to point users to this section, which
could include description of scenarios in which the problem appears.

(info "(emacs) Customization")

-- 
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.

Message #14 received at 72733 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, tpeplt <tpeplt <at> gmail.com>
Cc: 72733 <at> debbugs.gnu.org
Subject: Re: bug#72733: 29.4; Warning message while attempting to view
 customization buffer
Date: Mon, 30 Sep 2024 00:12:12 -0700

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: tpeplt <tpeplt <at> gmail.com>
>> Date: Tue, 20 Aug 2024 10:19:05 -0400
>>
>> Emacs Maintainers,
>>
>>    Emacs 29.4 appears to be running some (uninitialized?) code when a
>> sequence of sub-menus is selected.  This results in a warning message
>> about something that an Emacs user has not selected.  Here is a recipe
>> for reproducing the problem.  I have run this several times and gotten
>> the same result each time.
>>
>> 1. $ emacs -Q
>>
>> 2. M-x customize RET
>>
>> 3. The *Customize Group: Emacs* buffer is displayed.  In this buffer,
>>    select "Programming" from the menu of the Emacs group.
>>
>> 4. The *Customize Group: Programming* buffer is displayed.  In this
>>    buffer, select "Languages" from the menu.
>>
>> 5. A *Warnings* buffer is displayed in a new window.  The following
>>    warning message is displayed in that buffer:
>>
>> ⛔ 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
>
> It's a known issue for which there's no simple solution.  We want
> users who load ruby-ts-mode to know that they lack the Ruby grammar
> library, which is what this warning is about.  And Customize loads
> ruby-ts-mode to allow its customization when you select Languages.
>
> We could perhaps shut up these specific warnings in that specific
> situation, but that doesn't seem clean.  And the warning is just a
> warning, and harmless.

Showing the warning doesn't seem very clean either.

Message #17 received at 72733 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: 72733 <at> debbugs.gnu.org, tpeplt <at> gmail.com
Subject: Re: bug#72733: 29.4; Warning message while attempting to view
 customization buffer
Date: Mon, 30 Sep 2024 15:28:01 +0300

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Mon, 30 Sep 2024 00:12:12 -0700
> Cc: 72733 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: tpeplt <tpeplt <at> gmail.com>
> >> Date: Tue, 20 Aug 2024 10:19:05 -0400
> >>
> >> Emacs Maintainers,
> >>
> >>    Emacs 29.4 appears to be running some (uninitialized?) code when a
> >> sequence of sub-menus is selected.  This results in a warning message
> >> about something that an Emacs user has not selected.  Here is a recipe
> >> for reproducing the problem.  I have run this several times and gotten
> >> the same result each time.
> >>
> >> 1. $ emacs -Q
> >>
> >> 2. M-x customize RET
> >>
> >> 3. The *Customize Group: Emacs* buffer is displayed.  In this buffer,
> >>    select "Programming" from the menu of the Emacs group.
> >>
> >> 4. The *Customize Group: Programming* buffer is displayed.  In this
> >>    buffer, select "Languages" from the menu.
> >>
> >> 5. A *Warnings* buffer is displayed in a new window.  The following
> >>    warning message is displayed in that buffer:
> >>
> >> ⛔ 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
> >
> > It's a known issue for which there's no simple solution.  We want
> > users who load ruby-ts-mode to know that they lack the Ruby grammar
> > library, which is what this warning is about.  And Customize loads
> > ruby-ts-mode to allow its customization when you select Languages.
> >
> > We could perhaps shut up these specific warnings in that specific
> > situation, but that doesn't seem clean.  And the warning is just a
> > warning, and harmless.
> 
> Showing the warning doesn't seem very clean either.

Indeed.  But all the other solutions were either much more complex or
concealed the warning in important cases.

Message #20 received at 72733 <at> debbugs.gnu.org (full text, mbox):

From: Phil Sainty <psainty <at> orcon.net.nz>
To: 72733 <at> debbugs.gnu.org
Subject: Re: bug#72733: 29.4; Warning message while attempting to view
 customization buffer
Date: Mon, 20 Jan 2025 23:51:24 +1300

The case of `customize-changed' can be especially spammy with
these warnings.  I'm using GNU Emacs 30.0.93, and if I ask for
the changes since 28.1 then I get 15 warnings, each of which
is more than a kilobyte of text.

I'd say it's fairly likely that the user isn't particularly
interested in tree-sitter when using this command; but running
this command might be one of the first things they do after
upgrading, so it could easily look like problem with the new
version; especially if this is the first time they've used a
build with tree-sitter support.

If any exceptions are being considered, I think there's a
good case for `customize-changed' being one of them.


> And the warning is just a warning, and harmless.

Given that it's quite easy to trigger this in very tangential
ways, perhaps the warning should actually say that in order to
alleviate any concerns that users might have?

E.g.:  "If you are not using FOO-ts-mode then this warning can
safely be ignored."


-Phil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.