public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "René Berber" <rene.berber@gmail.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXTERNAL] Re: mintty mouse behavior with vim
Date: Fri, 12 May 2023 14:02:16 +0000	[thread overview]
Message-ID: <DM8PR09MB7095C3F095AAFE8F933FD307A5759@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
In-Reply-To: <13829598-2210-27d1-87ad-e62d68d81ba5@gmail.com>

> > You expect too much of ssh. ssh is a text utility, not an X one. The remote vim
> > never sees your mouse actions: it's mintty that performs select / paste.
> 
> Are you sure?
> 
> man ssh:
> 
> "     -X      Enables X11 forwarding.  This can also be specified on a
> per-host basis in a configuration file."

X11 forwarding has nothing to do with mouse tracking on the Cygwin terminal window.
Rather, it's a tunnel for the X applications (running on the remote host) that
allows them to use a local X11 server (XFree86, XWin32, MobaXTerm etc),
which in turn can display the application's window on your PC's desktop
(such as an xterm window with the remote host's shell in it)

HTH,

Anton Lavrentiev
Contractor NIH/NLM/NCBI


      parent reply	other threads:[~2023-05-12 14:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 15:24 Jose Isaias Cabrera
2023-05-11 18:23 ` Brian Inglis
2023-05-11 18:44   ` Jose Isaias Cabrera
2023-05-11 21:25     ` Gary Johnson
2023-05-12 16:38     ` Brian Inglis
2023-05-12 22:22       ` Jose Isaias Cabrera
2023-05-18 14:21         ` Jose Isaias Cabrera
2023-05-18 21:12           ` Brian Inglis
2023-05-18 22:11             ` Jose Isaias Cabrera
2023-05-19  7:53               ` Thomas Wolff
2023-05-12  2:16 ` mintty " Duncan Roe
2023-05-12  2:42   ` René Berber
2023-05-12  3:04     ` Brian Inglis
2023-05-12 14:02     ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [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=DM8PR09MB7095C3F095AAFE8F933FD307A5759@DM8PR09MB7095.namprd09.prod.outlook.com \
    --to=lavr@ncbi.nlm.nih.gov \
    --cc=cygwin@cygwin.com \
    --cc=rene.berber@gmail.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).