Re: native-comp *Warnings* buffer

[Eric Abrahamsen <eric@ericabrahamsen.net>]

On May 14, 2021 9:46:41 AM PDT, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>
>On May 14, 2021 9:23:50 AM PDT, Stefan Monnier
><monnier@iro.umontreal.ca> wrote:
>>> 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.
>>
>>I think "stealth" compilation performed opportunistically in the
>>background should indeed not display any warnings (by default).
>>
>>> 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).
>>
>>Don't those buttons also suppress the warnings for the normal
>>(non-async, non-native) compilation case?  If so, we should be careful
>>not to encourage the users to do that when they're only annoyed by the
>>async warnings.
>
>The buttons will add '(comp) to the list of suppressed warnings, so no
>warnings with that tag would ever be popped-up, in any context. I'm not
>sure what else uses that tag (I'm on my phone right now) but yes, that
>might be a little drastic.

If anyone else does use 'comp, we could have comp.el use '(comp async), which seems nicely targeted.