public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Duncan Roe <duncan_roe@optusnet.com.au>
To: cygwin@cygwin.com
Subject: Re: mintty mouse behavior with vim
Date: Fri, 12 May 2023 12:16:15 +1000	[thread overview]
Message-ID: <ZF2hbyv9uE/XtFtv@slk15.local.net> (raw)
In-Reply-To: <DB9P251MB006383EC72F6198A45FC248EDE749@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM>

On Thu, May 11, 2023 at 03:24:18PM +0000, cygwin wrote:
>
> Greetings.
>
> In mintty, while using vim, I would like to highlight a few lines, and
> have vim tell me how many lines have been highlighted. Is this a
> possibility? For example:
>
> 0
> 1
> ->2
> ->3
> ->4
> ->5
> 6
> 7
> 8
> 9
>
> If I highlight lines 2 through 5, I would like vim to tell me that 4
> lines have been highlighted. It works fine with the windows vim, but it
> does not want to do it through mintty. Thoughts? Thanks.
>
> José
>
> PS: The real problem is that I am ssh'ing to an ubuntu box which I am
> using vim, but the mouse is not being acknowledged. Although, I can
> highlight and copy/paste, but clicking to a word to move the cursor
> there, it's not acknowledged.
>
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.

Cheers ... Duncan.

  parent reply	other threads:[~2023-05-12  2:16 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 ` Duncan Roe [this message]
2023-05-12  2:42   ` mintty " René Berber
2023-05-12  3:04     ` Brian Inglis
2023-05-12 14:02     ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]

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=ZF2hbyv9uE/XtFtv@slk15.local.net \
    --to=duncan_roe@optusnet.com.au \
    --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).