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

Previous Next

Package: emacs;

Reported by: tpeplt <tpeplt <at> gmail.com>

Date: Tue, 20 Aug 2024 14:23:01 UTC

Severity: normal

Found in version 29.4

Full log


View this message in rfc822 format

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: 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.




This bug report was last modified 206 days ago.

Previous Next


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