public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: n952162 <n952162@web.de>
To: cygwin@cygwin.com
Subject: Re: Bug report for cygwin X server (or xterm)
Date: Wed, 30 Mar 2022 09:56:51 +0200	[thread overview]
Message-ID: <78adedda-082f-26b8-3ab6-de8edccd0f71@web.de> (raw)
In-Reply-To: <0c793a07-deef-da10-1108-0de8802c5c5f@web.de>

Am 10.03.2022 um 10:37 schrieb n952162:
> xterm*VT100.Translations only when mouse is over the window with focus
>
> Discovered with click-to-focus, in FVWM
>
> In particular, I'm talking about the function keys. In this case, these
> are NOT mapped in fvwm, but in xterm.
>
> Pressing a function key, like F1, always writes to the window with
> focus, but only performs the X11/xterm translations when the mouse is
> hovering over the window with focus.
>
> So, I always have to move the mouse to the window to be able to write to
> the window. Otherwise, \e[P is written to the window, for example
>
> Note that I can visit various windows with keyboard shortcuts, so
> there's no natural correspondence with mouse position and window focus.
>
> This failure to do the X11/xterm translation only occurs with x11/cygwin
> xterms. Windows opened locally via sshd (port forwarded) behave
> normally, performing the translation to the focused window, no matter
> where the mouse is.
>

This last point leads me to the conclusion that this is perhaps a
porting problem of the xterm virtual terminal program, because when
xterm is executing on another machine, it doesn't happen.



      reply	other threads:[~2022-03-30  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10  9:37 n952162
2022-03-30  7:56 ` n952162 [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:
  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=78adedda-082f-26b8-3ab6-de8edccd0f71@web.de \
    --to=n952162@web.de \
    --cc=cygwin@cygwin.com \
    /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).