From: Stefan Kangas <stefan@marxist.se>
To: martin rudalics <rudalics@gmx.at>
Cc: "André Marçais" <andre@marcais.net>, 36089@debbugs.gnu.org
Subject: bug#36089: 26.2; Emacs window creation with multiple frames
Date: Tue, 25 Aug 2020 17:46:34 -0700 [thread overview]
Message-ID: <CADwFkmkoJpEvNkWbbsZ7UM+EriwgxTztKFHrojy3D21WRRvoXw@mail.gmail.com> (raw)
In-Reply-To: <53b6e204-b0db-dca3-2bba-7aba65f04d0b@gmx.at> (martin rudalics's message of "Wed, 5 Jun 2019 09:13:46 +0200")
tags 36089 + notabug
close 36089
thanks
martin rudalics <rudalics@gmx.at> writes:
>> When I go to compile a program using M-x compile it shows the
>> *compilation* buffer in a new window in the active frame, which is
>> intuitive when there is only one frame open. However, in Emacs I often
>> have multiple frames open and visible (like with a multi monitor
>> setup). In this case Emacs still opens the *compilation* buffer in the
>> active frame even if the buffer is visible in another frame.
>
> Customize 'display-buffer-alist' as, for example,
>
> (customize-set-variable
> 'display-buffer-alist
> '(("\\*compilation\\*"
> nil (reusable-frames . visible))))
>
> For further options have a look at section
>
> 28.13.5 Precedence of Action Functions
>
> of the Elisp manual (and tell us if you think something is missing
> there).
>
> Thanks, martin
So this is all configurable, as explained above. There has also been no
further update within 1 year, so I'm closing this bug report now.
If this conclusion is incorrect and this is still an issue, please reply
to this email (use "Reply to all" in your email client) and we can
reopen the bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-08-26 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 13:21 bug#36089: 26.2; Emacs window creation with multiple frames André Marçais
2019-06-05 7:13 ` martin rudalics
2020-08-26 0:46 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkoJpEvNkWbbsZ7UM+EriwgxTztKFHrojy3D21WRRvoXw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=36089@debbugs.gnu.org \
--cc=andre@marcais.net \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.