unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Skip Montanaro <skip.montanaro@gmail.com>
To: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Can Emacs help here (running on Linux, display on Windows)?
Date: Fri, 4 Aug 2017 15:26:21 -0500	[thread overview]
Message-ID: <CANc-5Uz_=P-UL+e6dAdVw2rZPQ+56YsaPTx3-PxZ-hQzXycY=A@mail.gmail.com> (raw)

One thing I liked about the Mac was that click-to-focus meant exactly that.
If you hovered your mouse over a window which didn't have keyboard focus
and clicked, it changed keyboard focus, full stop. Said focus-changing
click was not also sent to the application. On Linux systems there is a
wide enough variety of window managers and one can either switch from
click-to-focus to focus-follows-mouse, or find a window manager which "does
the right thing."

Windows, not so much. I'd never used Windows until landing at my latest
job. Despite the fact that they employed me to write software for and on
Linux, they placed this Windows computer on my desk. Consequently, I
generally run with a bunch of PuTTY windows connected to Linux servers.
From one of those windows I fire up my beloved Emacs with DISPLAY set back
to the Windows machine. (The Windows desktop machine runs something called
VcXsrv as an X11 server.)

I'm now faced with a small problem. Click-to-focus is the rule, but stupid,
stupid Windows also insists on passing the same click used to change focus
to the application itself. Maybe VcXsrv has some setting I've not
discovered (I can't even find the damn thing on the computer.) Is there
some way to make it stop? Can Emacs come to the rescue and somehow ignore
that initial, point-changing click?

Thx,

Skip Montanaro


             reply	other threads:[~2017-08-04 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 20:26 Skip Montanaro [this message]
2017-08-05  6:38 ` Can Emacs help here (running on Linux, display on Windows)? Eli Zaretskii
2017-08-05  9:29   ` ken
2017-08-05 19:14   ` Bob Proulx
2017-08-05 19:39     ` Skip Montanaro
2017-08-05 20:48       ` Bob Proulx
2017-08-05 21:06         ` Óscar Fuentes
2017-08-05 19:51 ` Stefan Monnier
2017-08-05 21:07   ` Skip Montanaro
2017-08-05 20:04 ` Yuri Khan
2017-08-05 20:59   ` Skip Montanaro
2017-08-06  7:26   ` Emanuel Berg

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='CANc-5Uz_=P-UL+e6dAdVw2rZPQ+56YsaPTx3-PxZ-hQzXycY=A@mail.gmail.com' \
    --to=skip.montanaro@gmail.com \
    --cc=help-gnu-emacs@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.
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).