From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: native-comp *Warnings* buffer
Date: Fri, 14 May 2021 09:46:41 -0700 [thread overview]
Message-ID: <9FD44165-1C86-49C7-9B9A-57E281E546D6@ericabrahamsen.net> (raw)
In-Reply-To: <jwvsg2p4798.fsf-monnier+emacs@gnu.org>
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.
next prev parent reply other threads:[~2021-05-14 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 19:59 native-comp *Warnings* buffer Eric Abrahamsen
2021-05-13 20:20 ` Eric Abrahamsen
2021-05-13 21:28 ` Andrea Corallo via Emacs development discussions.
2021-05-13 21:34 ` Eric Abrahamsen
2021-05-13 22:00 ` Eric Abrahamsen
2021-05-14 6:28 ` Eli Zaretskii
2021-05-14 2:30 ` T.V Raman
2021-05-14 6:42 ` Eli Zaretskii
2021-05-14 6:11 ` Eli Zaretskii
2021-05-14 15:44 ` Eric Abrahamsen
2021-05-14 16:23 ` Stefan Monnier
2021-05-14 16:46 ` Eric Abrahamsen [this message]
2021-05-14 16:54 ` Eric Abrahamsen
2021-05-15 5:33 ` Richard Stallman
2021-05-16 4:15 ` Eric Abrahamsen
2021-05-16 14:06 ` Jump to source of warning was " T.V Raman
2021-05-16 20:04 ` Andrea Corallo via Emacs development discussions.
2021-05-16 21:25 ` Eric Abrahamsen
2021-05-17 6:11 ` Andrea Corallo via Emacs development discussions.
2021-05-17 3:23 ` Richard Stallman
2021-05-17 6:16 ` Eli Zaretskii
2021-05-16 5:12 ` Stefan Monnier
2021-05-16 5:30 ` Eli Zaretskii
2021-05-16 6:03 ` Stefan Monnier
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=9FD44165-1C86-49C7-9B9A-57E281E546D6@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).