Bug 21952

Summary: middle-mouse paste no longer works as expected in vim
Product: Mageia Reporter: Ethan Merritt <eamerritt>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: marja11, ouaurelien
Version: 7Keywords: NEEDINFO
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: vim-8.0.388-1.mga6.src.rpm CVE:
Status comment:

Description Ethan Merritt 2017-10-27 20:07:10 CEST
Description of problem:

vim now interprets Middle-mouse paste operation as "change to edit mode"+paste, which makes it impossible to paste commands (as opposed to text) into a vim session. This is a regression from behaviour of vim in previous versions. This issue has also been reported against vim in other distros but it is not clear to me from those trackers whether the issue is due to a change in the build options or a change in the vim source code.  Either way it is a regression.
See:
    https://bugs.gentoo.org/625590
May or may not be relevant:
    https://bugzilla.redhat.com/show_bug.cgi?id=1401410

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



VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Mar  2 2017 21:09:22)
Included patches: 1-388
Compiled by akien <akien>
Huge version without GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_old_static
+arabic          +find_in_path    -mouse_sysmouse  -tag_any_white
+autocmd         +float           +mouse_urxvt     +tcl
-balloon_eval    +folding         +mouse_xterm     +termguicolors
-browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +gettext         -mzscheme        +textobjects
+channel         -hangul_input    +netbeans_intg   +timers
+cindent         +iconv           +num64           +title
-clientserver    +insert_expand   +packages        -toolbar
-clipboard       +job             +path_extra      +user_commands
+cmdline_compl   +jumplist        +perl            +vertsplit
+cmdline_hist    +keymap          +persistent_undo +virtualedit
+cmdline_info    +lambda          +postscript      +visual
+comments        +langmap         +printer         +visualextra
+conceal         +libcall         +profile         +viminfo
+cryptv          +linebreak       +python/dyn      +vreplace
+cscope          +lispindent      +python3/dyn     +wildignore
+cursorbind      +listcmds        +quickfix        +wildmenu
+cursorshape     +localmap        +reltime         +windows
+dialog_con      -lua             +rightleft       +writebackup
+diff            +menu            +ruby            -X11
+digraphs        +mksession       +scrollbind      -xfontset
-dnd             +modify_fname    +signs           -xim
-ebcdic          +mouse           +smartindent     -xpm
+emacs_tags      -mouseshape      +startuptime     -xsmp
+eval            +mouse_dec       +statusline      -xterm_clipboard
+ex_extra        +mouse_gpm       -sun_workshop    -xterm_save
+extra_search    -mouse_jsbterm   +syntax          
+farsi           +mouse_netterm   +tag_binary      
   system vimrc file: "/etc/vim/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -g -pipe -Wformat -Werror=format-security -fstack-protector --param=ssp-buffer-size=4 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1       
Linking: gcc   -L. -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -Wl,--enable-new-dtags -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E   -L/usr/local/lib -Wl,--as-needed -o vim        -lm -ltinfo -lnsl    -lacl -lattr -lgpm -ldl   -Wl,-E  -fstack-protector-strong -L/usr/local/lib64  -L/usr/lib/perl5/5.22.3/x86_64-linux-thread-multi/CORE -lperl -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc   -L/usr/lib64 -ltcl8.6 -ldl -lz -lpthread -lieee -lm -lruby -lpthread -ldl -lcrypt -lm  -L/usr/lib64    



How reproducible:

100%


Steps to Reproduce:
1. Open existing file from konsole window, e.g. "vim foo.txt"
2. Select something using the x clipboard (could be from anywhere, not necessarily the vim window)
3. middle-mouse click in the vim window

vim will enter edit mode and insert the paste selection as text.
Desired behavious is instead to execute the paste selection as a command, just as if it were typed on the keyboard.

executing "set mouse=" or "set mouse=v"
Comment 1 Ethan Merritt 2017-10-27 20:08:54 CEST
sorry. incomplete last line.

executing "set mouse=" or "set mouse=v" does not change the behaviour.
Comment 2 Marja Van Waes 2017-10-27 20:19:50 CEST
Assigning to the registered Vim maintainer.

Assignee: bugsquad => thierry.vignaud
CC: (none) => marja11

Comment 3 Thierry Vignaud 2017-10-28 04:05:46 CEST
Have you tried "set mouse-=a" in your .vimrc file?

Keywords: (none) => NEEDINFO

Comment 4 Ethan Merritt 2017-10-28 05:25:44 CEST
Yes. No difference.  

I think the "set mouse" options are orthogonal to this problem. They control whether or not a mouse event is accepted (or at least they are supposed to do that. I'm not sure they are working in the current version but that would be a separate problem). The issue here is that the program invariably changes the mode to "edit" when it accepts the middle-mouse event.  If I disable acceptance I would be left with no paste at all rather than a paste into the wrong terminal mode.
Comment 5 Aurelien Oudelet 2020-08-05 16:39:02 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD

Comment 6 Ethan Merritt 2020-08-06 07:34:00 CEST
Still present in version 7 and in Cauldron

Resolution: OLD => (none)
Version: 6 => 7
Status: RESOLVED => REOPENED

Comment 7 Aurelien Oudelet 2021-07-06 13:17:57 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 8 Marja Van Waes 2021-09-07 14:09:01 CEST
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: REOPENED => RESOLVED
Resolution: (none) => OLD