From: Stefan Kangas <stefan@marxist.se>
To: No Wayman <iarchivedmywholelife@gmail.com>
Cc: 46025@debbugs.gnu.org
Subject: bug#46025: 28.0.50; warning suppression buttons truncate warnings
Date: Tue, 20 Apr 2021 22:19:31 -0500 [thread overview]
Message-ID: <CADwFkmmGnS-h+5cv9DQX_3DU0dOAXPEtD4bykXSSwGYMjc2R1g@mail.gmail.com> (raw)
In-Reply-To: <87im7qvwpl.fsf@gmail.com> (No Wayman's message of "Thu, 21 Jan 2021 15:51:09 -0500")
No Wayman <iarchivedmywholelife@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)?
next prev parent reply other threads:[~2021-04-21 3:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 20:51 bug#46025: 28.0.50; warning suppression buttons truncate warnings No Wayman
2021-01-22 9:12 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-22 22:05 ` No Wayman
2021-04-21 3:19 ` Stefan Kangas [this message]
2021-04-21 8:58 ` Eli Zaretskii
2021-04-21 11:39 ` iarchivedmywholelife
2022-07-28 12:39 ` Lars Ingebrigtsen
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=CADwFkmmGnS-h+5cv9DQX_3DU0dOAXPEtD4bykXSSwGYMjc2R1g@mail.gmail.com \
--to=stefan@marxist.se \
--cc=46025@debbugs.gnu.org \
--cc=iarchivedmywholelife@gmail.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).