From: Juri Linkov <juri@linkov.net>
To: Kiso Katsuyuki <katsuyuki2388@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Selecting *Compile-log* buffer automatically
Date: Mon, 11 Dec 2023 19:04:39 +0200 [thread overview]
Message-ID: <86wmtlrqpc.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAOq35dggbbves9tsnN-cL6wjkptXrZBVHFqqv3Gk2oNUDsouEg@mail.gmail.com> (Kiso Katsuyuki's message of "Sun, 10 Dec 2023 12:38:22 -0600")
> I recently found that I had been moving focus to the *Compile-log* buffer
> and burying it after byte-compiling an elisp file.
> Selecting *Compile-log* buffer automatically reduces commands to do this.
> After my investigation on bytecomp.el and warning.el, there seems to be no
> option to select the *Compile-log* buffer automatically
> when it shows up in the active frame.
>
> Does it make sense to do
> - On byte-compiling an elisp file, select the byte-compile-log-buffer
> window automatically if the buffer is visible, and
> - Add a variable to switch the function enable/disable.
> ?
I believe this should be customizable with something like
(setopt display-buffer-alist
'(("\\*Compile-log\\*" nil (select-window . t))))
next prev parent reply other threads:[~2023-12-11 17:04 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
2023-12-17 2:22 ` Kiso Katsuyuki
2023-12-11 17:04 ` Juri Linkov [this message]
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=86wmtlrqpc.fsf@mail.linkov.net \
--to=juri@linkov.net \
--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).