From: emacser via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: "45844@debbugs.gnu.org" <45844@debbugs.gnu.org>
Subject: bug#45844: 27.1; unwanted raising of other frame when emacs is in the backgound and switch-to-buffer is used in a dedicated frame
Date: Wed, 13 Jan 2021 18:49:13 +0000 [thread overview]
Message-ID: <abtBkPnB-4go5DpZ7HLlnWDN2MOETsEf0Zp6YAdt-NeXj-oJs_KD7kj7RU9vPLsGKOF2rybUIa0UxJXduck0ra2X8u2_hkTVriCnRVjTwag=@protonmail.com> (raw)
In-Reply-To: <698ea7a3-c2b2-7705-3fc4-16d52c8a7acd@gmx.at>
>
> And 'pop-to-buffer' makes a new frame because it cannot use the selected
> one, raises that frame and even requests input focus for it.
There is no need to create a new frame, since the other frame exists in my case,
but if pop-to-buffer raises that automatically then it's understandable why
it comes to the foreground.
A possible solution for this can be checking if pop-to-buffer is called interactively
by the user. If so then it calls select-frame-set-input-focus like now, if not
then it calls select-frame instead.
next prev parent reply other threads:[~2021-01-13 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 17:08 bug#45844: 27.1; unwanted raising of other frame when emacs is in the backgound and switch-to-buffer is used in a dedicated frame emacser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-13 17:17 ` emacser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-13 18:07 ` martin rudalics
2021-01-13 18:49 ` emacser via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-01-14 7:40 ` martin rudalics
2021-01-14 8:20 ` emacser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14 9:26 ` martin rudalics
2021-01-14 9:39 ` emacser via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-21 3:35 ` Stefan Kangas
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='abtBkPnB-4go5DpZ7HLlnWDN2MOETsEf0Zp6YAdt-NeXj-oJs_KD7kj7RU9vPLsGKOF2rybUIa0UxJXduck0ra2X8u2_hkTVriCnRVjTwag=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=45844@debbugs.gnu.org \
--cc=laszlomail@protonmail.com \
--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 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).