From: Chong Yidong <cyd@stupidchicken.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Stephen Berman <stephen.berman@gmx.net>, 2025@debbugs.gnu.org
Subject: bug#2025: 23.0.60; emacsclient: frame does not get focus on opening
Date: Wed, 05 Oct 2011 17:50:42 -0400 [thread overview]
Message-ID: <87aa9f3y6l.fsf@stupidchicken.com> (raw)
In-Reply-To: <4E8CA7F6.207@swipnet.se> ("Jan \=\?utf-8\?Q\?Dj\=C3\=A4rv\=22's\?\= message of "Wed, 05 Oct 2011 20:54:46 +0200")
Jan Djärv <jan.h.d@swipnet.se> writes:
> A hint is just a hint, the WM may do as it please anyway. It is
> considered bad behaviour to try to steal input focus when started. It
> should depend on what policy the user has set, focus-follows-mouse or
> click-to-focus.
>
> If Emacs is started with focus-follows-mouse and the mouse isn't in a
> frame, I would expect Emacs not to have focus. However, some WMs warp
> the mouse to newly started applications. For click-to-focus I think
> the WM just does what it thinks is best. Some WMs have a setting
> ("give focus to new window") which the user can use to influence this.
>
> So to conclude, if Emacs where to try do anything, there are window
> managers where this would fail anyway. Better if the OP can get KWin
> to behave. Maybe there is some option for this in KWin.
According to teh Google, the Kwin setting in question is called "focus
stealing prevention level", which should be set to "none" to allow
newly-launched applications to acquire focus.
next prev parent reply other threads:[~2011-10-05 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 15:16 bug#2025: 23.0.60; emacsclient: frame does not get focus on opening Stephen Berman
2011-10-05 4:48 ` Glenn Morris
2011-10-05 8:31 ` Stephen Berman
2011-10-05 17:15 ` Glenn Morris
2011-10-05 18:54 ` Jan Djärv
2011-10-05 21:33 ` Glenn Morris
2011-10-05 21:50 ` Chong Yidong [this message]
2011-10-05 22:19 ` Stephen Berman
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=87aa9f3y6l.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=2025@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=stephen.berman@gmx.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 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.