From: Eli Zaretskii <eliz@gnu.org>
To: Kiso Katsuyuki <katsuyuki2388@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Selecting *Compile-log* buffer automatically
Date: Mon, 11 Dec 2023 13:56:02 +0200 [thread overview]
Message-ID: <83plzduf59.fsf@gnu.org> (raw)
In-Reply-To: <CAOq35diiibWgL6H-aMznn-0-QRvCV1JoxX347O_2huz_RVKOGQ@mail.gmail.com> (message from Kiso Katsuyuki on Sun, 10 Dec 2023 19:07:31 -0600)
> From: Kiso Katsuyuki <katsuyuki2388@gmail.com>
> Date: Sun, 10 Dec 2023 19:07:31 -0600
> Cc: emacs-devel@gnu.org
>
> >Can you elaborate why you needed to select it? Emacs has commands to
> >scroll non-selected windows, you should be able to view the
> >compilation log without the need to select its window.
>
> In almost all my byte-compile, warnings like "Warning: assignment to free variable...",
> "Warning: the function ‘foo’ might not be defined at runtime", and etc. occur.
> Warnings and Errors have Emacs display the *Compile-log* buffer
> (this is the default behavior). I usually ignores this kind of warnings,
> so I just move focus to the *Compile-log* buffer window, bury it (keybind "q" by default),
> and then I can restore the original window configuration. I want to skip the step to move focus to
> the *Compile-log* buffer window.
So maybe we should indeed add an optional behavior, for those case.
Do you agree that the compile log window should be only selected if
there are actually warnings or errors during the last compilation?
next prev parent reply other threads:[~2023-12-11 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 18:38 Selecting *Compile-log* buffer automatically Kiso Katsuyuki
2023-12-10 19:32 ` Eli Zaretskii
2023-12-11 1:07 ` Kiso Katsuyuki
2023-12-11 11:56 ` Eli Zaretskii [this message]
2023-12-17 2:22 ` Kiso Katsuyuki
2023-12-11 17:04 ` Juri Linkov
2023-12-23 8:19 ` Kiso Katsuyuki
2023-12-23 17:41 ` Juri Linkov
2023-12-24 12:51 ` Kiso Katsuyuki
2023-12-24 17:28 ` Juri Linkov
2023-12-25 13:03 ` Kiso Katsuyuki
2024-02-17 18:20 ` Kiso Katsuyuki
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=83plzduf59.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=katsuyuki2388@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).