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: Thu, 14 Jan 2021 08:20:55 +0000 [thread overview]
Message-ID: <K2Oep1NSW9_pnWTBVOfE_066LNsKy8hxIFGq-KjZsDl0PY6nLauVE4d3tUU4MW0WDt0ieY5NsLz2GU2kolN0VPJZ-mwBPD3re8yotLe6Vjs=@protonmail.com> (raw)
In-Reply-To: <7420050f-39bc-61ce-5f04-706f0b63e3e8@gmx.at>
On Thursday, January 14, 2021 8:40 AM, martin rudalics <rudalics@gmx.at> wrote:
>
> Sorry but we can't do that.`switch-to-buffer' has to provide the window the next keystroke will be addressed to. That is carved in stone. I still don't understand why you insist on using`switch-to-buffer'
> here. Why don't you just call `display-buffer' if you don't want to
> edit that buffer anyway?
>
I'll try that, I only found it strange that if a background timer uses
switch-to-buffer and the frame is in in the background then why the frame
is raised. If it's not triggered by a user interaction then there is
no practical reason to bring the frame into the foreground, because the
user is using an other app, so he doesn't want to type into that frame
at that point. The frame should only switch to the buffer and remain in the
background, so when the user get backs to emacs then he can see the result
of the background process presented to him.
It sounds like a bug to me, but I accept if you say it's hard to implement
for some reason and I'll change my code to use an other method.
next prev parent reply other threads:[~2021-01-14 8:20 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
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 [this message]
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='K2Oep1NSW9_pnWTBVOfE_066LNsKy8hxIFGq-KjZsDl0PY6nLauVE4d3tUU4MW0WDt0ieY5NsLz2GU2kolN0VPJZ-mwBPD3re8yotLe6Vjs=@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).