public inbox for
help / color / mirror / Atom feed
From: Oliver Schmidt <>
Subject: Re: emacs holding focus, not granting it to xterm
Date: Sun, 29 Jun 2014 13:52:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 6/27/2014 11:22 PM, alflanagan wrote:
> The problem occurs when I run emacsclient to connect to an existing instance
> of emacs; the file shows up in emacs and emacsclient exits as expected, but
> focus remains "stuck" in emacs for some time.

I tried the following to reproduce the problem:

Under Cygwin X Server Version 1.15.1-3:

1.) Start an xterm under cygwin with xserver in multiwindow mode.
2.) From this cygwin xterm log into remote linux (debian 3.2.0-4-486) machine with "ssh -X".
3.) After logged in to the remote linux machine: start emacs with "emacs &". This opens a new X11 window under cygwin X server which is on top and has keyboard focus.
4.) In Emacs Window type the key combination Alt+X and then "server-start"
5.) Go back to xterm window and type: "emacsclient <filename> &" to edit the file <filename> in the emacs-server.
6.) Now: all typing goes inte the emacs X11 window, although this window is in the background (it might even be not visible if it is behind other windows).

It turns out that the above behaviour is the known problem that windows are not raised from the Cygwin X Server in multiwindow mode, if a program wants to programmatically activate a window as reported in .

If I start a modified xserver with my patch applied from the following happens in step 6:

6'.) the emacs window is raised to the top over all windows and gets the keyboard focus.

I think that 6'.) is the expected behaviour because this also happens if running under a x server on a  linux machine instead of cygwin.

Best regards,

Unsubscribe info:
Problem reports:

      reply	other threads:[~2014-06-29 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 11:45 Hans-Georg Scherneck
2014-06-02 14:00 ` Jon TURNEY
2014-06-02 17:49   ` Hans-Georg Scherneck
2014-06-27 21:22     ` alflanagan
2014-06-29 13:52       ` Oliver Schmidt [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.
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).