GNU bug report logs - #46025
28.0.50; warning suppression buttons truncate warnings

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 46025 in the body.
You can then email your comments to 46025 AT debbugs.gnu.org in the normal way.

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

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

From: No Wayman <iarchivedmywholelife <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 28.0.50; warning suppression buttons truncate warnings
Date: Thu, 21 Jan 2021 15:51:09 -0500

The warning suppression buttons introduced in 
66d01012ba61a364fe92cdc1728bfa135a90626a truncate warning 
messages.
I have offered a trivial patch in the past to have an option to 
disable these buttons:

https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-09/msg01405.html

Lars did not see it as a valid use case. His argument 
(summarized):

> since you get the warnings so seldom, it makes sense
> to have the very few you see come with ready-made ways of making 
> them go
> away, and then you're back to no warnings again.

Initially I thought the idea of the buttons was useful, but after 
thinking on it more
I agree with the case against these buttons Jonas Bernoulli made 
here:

https://lists.gnu.org/archive/html/emacs-devel/2020-11/msg00768.html

I would add to that, the fact that the buttons truncate the 
warning messages makes it impossible for a user to make an 
informed decision on whether or not they should be suppressing the 
warning. The truncated messages are equally useless to me as a 
developer. Here's an image someone sent me of the warnings on 
their system:

https://user-images.githubusercontent.com/2872862/105290265-42526580-5bb0-11eb-962d-b56f71b6efc0.png

While I politely encouraged them to send text in the future for 
such output,
here's what I would've received:

Warning (comp): Debugger entered--Lisp error: 
(native-compiler-error-empty-byte 
"/root/.emacs.d/straight/build/straight/straight-au..." 
"/root/.emacs.d/straight/build/straight/straight-au...\
") Disable showing Disable logging
Warning (comp): Debugger entered--Lisp error: 
(native-compiler-error-empty-byte 
"/root/.emacs.d/straight/build/bind-key/bind-key-au..." 
"/root/.emacs.d/straight/build/bind-key/bind-key-au...\
") Disable showing Disable logging
Warning (comp): Debugger entered--Lisp error: 
(native-compiler-error-empty-byte 
"/root/.emacs.d/straight/build/use-package/use-pack..." 
"/root/.emacs.d/straight/build/use-package/use-pack...\
") Disable showing Disable logging

It's only by luck I can see enough of the file path to know which 
files are throwing the errors.

Is there a way to work around this (absent my patch)?

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

From: Andrea Corallo <akrl <at> sdf.org>
To: No Wayman <iarchivedmywholelife <at> gmail.com>
Cc: 46025 <at> debbugs.gnu.org
Subject: Re: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Fri, 22 Jan 2021 09:12:09 +0000

No Wayman <iarchivedmywholelife <at> gmail.com> writes:

> The warning suppression buttons introduced in
> 66d01012ba61a364fe92cdc1728bfa135a90626a truncate warning messages.
> I have offered a trivial patch in the past to have an option to
> disable these buttons:
>
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-09/msg01405.html
>
> Lars did not see it as a valid use case. His argument (summarized):
>
>> since you get the warnings so seldom, it makes sense
>> to have the very few you see come with ready-made ways of making
>> them go
>> away, and then you're back to no warnings again.
>
> Initially I thought the idea of the buttons was useful, but after
> thinking on it more
> I agree with the case against these buttons Jonas Bernoulli made here:
>
> https://lists.gnu.org/archive/html/emacs-devel/2020-11/msg00768.html
>
> I would add to that, the fact that the buttons truncate the warning
> messages makes it impossible for a user to make an informed decision
> on whether or not they should be suppressing the warning. The
> truncated messages are equally useless to me as a developer. Here's an
> image someone sent me of the warnings on their system:
>
> https://user-images.githubusercontent.com/2872862/105290265-42526580-5bb0-11eb-962d-b56f71b6efc0.png
>
> While I politely encouraged them to send text in the future for such
> output,
> here's what I would've received:
>
> Warning (comp): Debugger entered--Lisp error:
> (native-compiler-error-empty-byte
> "/root/.emacs.d/straight/build/straight/straight-au..."
> "/root/.emacs.d/straight/build/straight/straight-au...\
> ") Disable showing Disable logging
> Warning (comp): Debugger entered--Lisp error:
> (native-compiler-error-empty-byte
> "/root/.emacs.d/straight/build/bind-key/bind-key-au..."
> "/root/.emacs.d/straight/build/bind-key/bind-key-au...\
> ") Disable showing Disable logging
> Warning (comp): Debugger entered--Lisp error:
> (native-compiler-error-empty-byte
> "/root/.emacs.d/straight/build/use-package/use-pack..."
> "/root/.emacs.d/straight/build/use-package/use-pack...\
> ") Disable showing Disable logging
>
> It's only by luck I can see enough of the file path to know which
> files are throwing the errors.
>
> Is there a way to work around this (absent my patch)?

Hi,

is using the full output in the *Async-native-compile-log* buffer an
acceptable alternative?

Regards

  Andrea

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

From: No Wayman <iarchivedmywholelife <at> gmail.com>
To: Andrea Corallo <akrl <at> sdf.org>
Cc: 46025 <at> debbugs.gnu.org
Subject: Re: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Fri, 22 Jan 2021 17:05:11 -0500

Andrea Corallo <akrl <at> sdf.org> writes:
>
> Hi,
>
> is using the full output in the *Async-native-compile-log* 
> buffer an
> acceptable alternative?
>
> Regards
>
>   Andrea

Hi, Andrea.

That's a workaround for the time being and I appreciate the 
advice.

Long term, I think Stefan's idea of educating users on the nature 
of the
warnings and encouraging them to report them to package 
maintainers seems like a
better solution than encouraging them to sweep warnings under the 
rug.

~ Nick

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

From: Stefan Kangas <stefan <at> marxist.se>
To: No Wayman <iarchivedmywholelife <at> gmail.com>
Cc: 46025 <at> debbugs.gnu.org
Subject: Re: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Tue, 20 Apr 2021 22:19:31 -0500

No Wayman <iarchivedmywholelife <at> gmail.com> writes:

> The warning suppression buttons introduced in
> 66d01012ba61a364fe92cdc1728bfa135a90626a truncate warning messages.
> I have offered a trivial patch in the past to have an option to disable these
> buttons:
>
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-09/msg01405.html
>
> Lars did not see it as a valid use case. His argument (summarized):
>
>> since you get the warnings so seldom, it makes sense
>> to have the very few you see come with ready-made ways of making them go
>> away, and then you're back to no warnings again.
>
> Initially I thought the idea of the buttons was useful, but after thinking on it
> more
> I agree with the case against these buttons Jonas Bernoulli made here:
>
> https://lists.gnu.org/archive/html/emacs-devel/2020-11/msg00768.html
>
> I would add to that, the fact that the buttons truncate the warning messages
> makes it impossible for a user to make an informed decision on whether or not
> they should be suppressing the warning. The truncated messages are equally
> useless to me as a developer. Here's an image someone sent me of the warnings on
> their system:

Yes, it seems useless to have these buttons in their current form.

Could we at least disable them until they are fixed to not truncate
warnings?  They hide the contents of legitimate warnings.

> https://user-images.githubusercontent.com/2872862/105290265-42526580-5bb0-11eb-962d-b56f71b6efc0.png
>
> While I politely encouraged them to send text in the future for such output,
> here's what I would've received:
>
> Warning (comp): Debugger entered--Lisp error:  (native-compiler-error-empty-byte
> "/root/.emacs.d/straight/build/straight/straight-au..."
> "/root/.emacs.d/straight/build/straight/straight-au...\
> ") Disable showing Disable logging
> Warning (comp): Debugger entered--Lisp error:  (native-compiler-error-empty-byte
> "/root/.emacs.d/straight/build/bind-key/bind-key-au..."
> "/root/.emacs.d/straight/build/bind-key/bind-key-au...\
> ") Disable showing Disable logging
> Warning (comp): Debugger entered--Lisp error: (native-compiler-error-empty-byte
> "/root/.emacs.d/straight/build/use-package/use-pack..."
> "/root/.emacs.d/straight/build/use-package/use-pack...\
> ") Disable showing Disable logging
>
> It's only by luck I can see enough of the file path to know which files are
> throwing the errors.
>
> Is there a way to work around this (absent my patch)?

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 46025 <at> debbugs.gnu.org, iarchivedmywholelife <at> gmail.com
Subject: Re: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Wed, 21 Apr 2021 11:58:21 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Tue, 20 Apr 2021 22:19:31 -0500
> Cc: 46025 <at> debbugs.gnu.org
> 
> Yes, it seems useless to have these buttons in their current form.
> 
> Could we at least disable them until they are fixed to not truncate
> warnings?  They hide the contents of legitimate warnings.

AFAIK, the warnings are only truncated when they are VERY long, as in
the case above, where they show the backtrace from the Lisp debugger.
Originally, there was a bug that would cause almost every message be
truncated, but that was fixed.

Not sure what to do with warnings that show backtraces.

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

From: iarchivedmywholelife <iarchivedmywholelife <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Stefan Kangas <stefan <at> marxist.se>
Cc: 46025 <at> debbugs.gnu.org
Subject: Re: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Wed, 21 Apr 2021 07:39:54 -0400

[Message part 1 (text/plain, inline)]

> Not sure what to do with warnings that show backtraces.Perhaps we could do something similar to what the backtrace buffer does. After a certain length, ellide the warning with the ellipses, but make the ellipses expandable so the whole message can be seen. We could, optionally include a command to expand all.

[Message part 2 (text/html, inline)]

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: No Wayman <iarchivedmywholelife <at> gmail.com>
Cc: 46025 <at> debbugs.gnu.org
Subject: Re: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Thu, 28 Jul 2022 14:39:16 +0200

No Wayman <iarchivedmywholelife <at> gmail.com> writes:

> The warning suppression buttons introduced in
> 66d01012ba61a364fe92cdc1728bfa135a90626a truncate warning messages.

I've now changed this to use less intrusive buttons in Emacs 29.

Previous Next

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