Re: native-comp *Warnings* buffer

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Thu, 13 May 2021 12:59:12 -0700
>> 
>> I understand the utility of having these warnings, but does the buffer
>> need to be popped up every thirty seconds?
>
> It only pops up if you delete the window, doesn't it?  So in what
> sense is it different from what we do with the *Compilation* buffer?

I guess usage. I only see the *Compilation* buffer when I've
done something to ask for it (updating packages, etc), and it's over
relatively quickly. These warnings went on for many long minutes, at
random intervals. I was trying to work in two side-by-side buffers, and
it kept stealing the other one -- I even switched frames once the
*Warnings* buffer was open, but it followed me to the new frame.

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Thu, 13 May 2021 14:34:40 -0700
>> Cc: Andrea Corallo <akrl@sdf.org>
>> 
>> We could add 'suppress or 'quiet as an alternate value
>> `native-comp-async-report-warnings-errors', and use that to optionally
>> change the value of `warning-suppress-types'.
>
> Yes, this could be a good feature, for those who want this deferral up
> front, not via the buttons already present.

I could do a patch for that, but the existing mechanisms *are* pretty
thorough: big prominent buttons that do exactly what they promise to do
(I'm a bit embarrassed I didn't just read the instructions).