unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kiso Katsuyuki <katsuyuki2388@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: Selecting *Compile-log* buffer automatically
Date: Mon, 25 Dec 2023 07:03:26 -0600	[thread overview]
Message-ID: <CAOq35djfR=S4pUXEOYcb_BrfP3RxMr8x0TMbNsDOiKNGuJwcPQ@mail.gmail.com> (raw)
In-Reply-To: <86o7efse5r.fsf@mail.linkov.net>

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

>Indeed, you can't select arbitrary windows in every display-buffer,
>because code after every display-buffer expects certain buffers
>to be selected.  This was discussed in bug#33258, and the only
>possible solution is to select the window when the current command
>finishes.  This is implemented in bug#67993.

I checked #67993, used the patch, and the *Compile-Log* buffer was selected
successfully without the error. If #67993 is implemented, I'll use
display-buffer-alist.
Otherwise I'll modify bytecomp.el without using display-buffer-alist.
I figured out that the post-command-hook is useful.

[-- Attachment #2: Type: text/html, Size: 682 bytes --]

  reply	other threads:[~2023-12-25 13:03 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
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 [this message]
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='CAOq35djfR=S4pUXEOYcb_BrfP3RxMr8x0TMbNsDOiKNGuJwcPQ@mail.gmail.com' \
    --to=katsuyuki2388@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).