From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 29518@debbugs.gnu.org
Subject: bug#29518: 27.0.50; Compilation errors grab frame focus
Date: Thu, 30 Nov 2017 16:29:56 -0800 [thread overview]
Message-ID: <87609rs323.fsf@ericabrahamsen.net> (raw)
I've noticed over the past few weeks (couple of months?) that, while
updating packages, any compilation errors result in the *Package List*
frame grabbing focus.
I start a package upgrade, switch to some other program, and then (some
packages produce a lot of errors!) start a focus tug-of-war with the
Emacs frame where the compilation is going on.
I am on arch linux, with no DE, running i3 directly on X. I note that if
I move to a different workspace, compilation errors cause the workspace
where the frame lives to turn red (which seems to be the i3 behavior for
frames with warnings or notifications or whatever the X terminology is),
but I'm not yanked back there. If I'm in that workspace, however, the
Emacs frame keeps jumping to the fore.
I've looked through the Emacs git log to see if anything jumps out as
having been changed, but most of the frame/focus stuff seems NS-related.
But I'm pretty sure this is new behavior.
In GNU Emacs 27.0.50 (build 13, x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
of 2017-11-30 built on slip
Repository revision: 3f3d98ee5851840228786390ee7dbf851d144eb8
Windowing system distributor 'The X.Org Foundation', version 11.0.11905000
next reply other threads:[~2017-12-01 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 0:29 Eric Abrahamsen [this message]
2018-01-06 14:50 ` bug#29518: 27.0.50; Compilation errors grab frame focus Noam Postavsky
2018-01-06 20:13 ` Eric Abrahamsen
2018-01-06 20:31 ` Noam Postavsky
2018-01-15 4:40 ` Eric Abrahamsen
2018-01-15 12:07 ` Noam Postavsky
2018-01-16 0:15 ` Eric Abrahamsen
2022-01-23 15:51 ` Lars Ingebrigtsen
2022-01-24 1:04 ` Eric Abrahamsen
2022-01-24 9:42 ` Lars Ingebrigtsen
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=87609rs323.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=29518@debbugs.gnu.org \
/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).