unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: native-comp *Warnings* buffer
Date: Thu, 13 May 2021 12:59:12 -0700	[thread overview]
Message-ID: <87k0o2z9pr.fsf@ericabrahamsen.net> (raw)

I understand the utility of having these warnings, but does the buffer
need to be popped up every thirty seconds? Couldn't it just be displayed
once, when it's created, and then left alone? Compilation has been going
on for several minutes since rebuilding Emacs, and it's actually hard to
use with *Warnings* occupying my other window every few seconds!

Thanks,
Eric




             reply	other threads:[~2021-05-13 19:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 19:59 Eric Abrahamsen [this message]
2021-05-13 20:20 ` native-comp *Warnings* buffer 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
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=87k0o2z9pr.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.org \
    /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).