public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Kevin Schnitzius <kometes@yahoo.com>
Subject: Re: vim paste bug with compatible and showmatch turned on (seen for at least a year)
Date: Tue, 04 Feb 2020 01:56:00 -0000	[thread overview]
Message-ID: <20200204105601.ecd64b60ed38c6a444ff8658@nifty.ne.jp> (raw)
In-Reply-To: <572769636.1425652.1580766080816@mail.yahoo.com>

On Mon, 3 Feb 2020 21:41:20 +0000 (UTC)
"Kevin Schnitzius via cygwin" wrote:
> 64-bit Cygwin, Win10, nothing special about my installation.
> 
> 
> Start vim cleanly inside a mintty window running bash (updated my installation today):
> /usr/bin/vim --clean -u /dev/nul test.txt
> 
> Insert the following string:
> "pIppp"
> 
> Copy that string into the paste buffer using the mouse and ctrl-insert.
> Insert the following string on the next line:
> "(char *) "
> 
> Then press shift-insert to paste. You should get:
> "(char *) pIppp"
> 
> This is normal behavior.
> 
> Press escape and then ":set sm cp" and press enter  Vim is now in compatible mode and showmatch is turned on.
> 
> Insert the following string on the next line:
> "(char *) "
> 
> Then press shift-insert to paste.  You should get the same string.  However, I get:
> "Ppp(char *)"
> 
> It seems like at least an ESC character is inserted, so the mode gets changed from insert to command.  This can be really destructive if you have a long buffer.
> 
> The showmatch mechanism is required to reproduce this bug.
> 
> Is this bug a Cygwin, vim, mintty, or something else bug?

This seems to be a upstream bug of vim. I tested several
version of vim and results are as follows.

8.0.707  in debian stretch OK
8.0.1567 in cygwin NG
8.1.1240 in cygwin NG
8.1.1401 in debian buster NG
8.1.1551 in debian buster (local build) NG
8.1.1772 in cygwin NG
8.2.100  in cygwin (local build) NG 

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2020-02-04  1:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <572769636.1425652.1580766080816.ref@mail.yahoo.com>
2020-02-03 21:41 ` Kevin Schnitzius via cygwin
2020-02-04  1:56   ` Takashi Yano [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=20200204105601.ecd64b60ed38c6a444ff8658@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=kometes@yahoo.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).