Bug 1411121 - vi default mouse behaviour has changed
Summary: vi default mouse behaviour has changed
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 24
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-08 14:50 UTC by Louis van Dyk
Modified: 2017-01-09 12:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-01-09 12:38:22 UTC
Type: Bug

Attachments (Terms of Use)

Description Louis van Dyk 2017-01-08 14:50:04 UTC
Description of problem:
All on its own (I suspect after the update mod-December) vim mouse default behaviour has changed.

In the past, I could hightlight text in vim, and middle-click-button paste it in another terminal window, or press "i" and paste it elsewhere in the file I am editing.

Now, it no longer does this.  Instead, when in insert mode it only pastes "p" when pressing the middle button, and when highlighting text to copy it, it goes into "visual" mode.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. vi filename-with-text
2. highlight the text to copy it - it goes displays "visual" at the bottom and text gets a grey background.  ESC to cancel.  I don't know what that is supposed to achieve!
3. press "i" or "o" or "a" to insert text.  Click the middle mouse button to paste.  It only pastes "p" no matter what's in the highlighted clipboard.

Actual results:
As above.

Expected results:
The highlight to copy and middle click to paste behaviour that we have had for years and years and years is what I expect.

Additional info:

Comment 1 Louis van Dyk 2017-01-08 14:53:18 UTC
Apologies - two other packages also installed - in total:

Comment 2 Zdenek Dohnal 2017-01-09 07:23:07 UTC
Hi Louis,

thank you for contacting us. Would you mind trying the newest vim's update (version 8.0.142-1)? It should solve this issue.

Comment 3 Louis van Dyk 2017-01-09 11:45:39 UTC

I pulled the trigger too soon it seems!

The latest update corrects the behaviour. 

Many thanks!  You may close this ticket.

Comment 4 Zdenek Dohnal 2017-01-09 12:38:22 UTC
No problem :) , closing it as CURRENTRELEASE.

Note You need to log in before you can comment on or make changes to this bug.