On 1/18/17 10:24 AM, Alexander Kabaev wrote: > On Wed, 18 Jan 2017 10:06:55 -0800 > Pete Wright <pete_at_nomadlogic.org> wrote: > >> On 1/18/17 10:01 AM, Julian Elischer wrote: >>> On 18/01/2017 5:03 PM, Raimund Sacherer wrote: >>>> I have to put mouse=v to get the behavior I am used to. >>>> >>>> Best >>> >>> doesn't really work for me. >>> >>> vim is still taking mouse events >>> >> >> kinda feel like it we need a "classic" vim port that is from the v7.x >> codebase since i suspect the changes to mouse behaviour in v8.x is >> only the beginning of lots of suspect changes to the vim codebase :/ >> >> i went through the code for vim the other day and couldn't figure out >> a way to disable entering visual-mode via mouseclick as a compile >> time option. perhaps we should preserve the expected behaviour by >> updating /usr/local/etc/vim/vimrc? >> I just applied this diff against my global vimrc file and it now disables the visual mode by default function: $ diff -u vimrc.sample vimrc --- vimrc.sample 2017-01-13 22:39:36.000000000 -0800 +++ vimrc 2017-01-18 10:51:48.020039000 -0800 _at__at_ -3,10 +3,10 _at__at_ endif let g:is_posix = 1 -set nocompatible set bs=indent,eol,start set history=50 set ruler +set mouse-=a if &t_Co > 2 || has("gui_running") syntax on I'm not %100 clear why it was setting "nocompatible" - but once I removed it it disabled visual-mode-on-mouse-click. I'll be managing this on my systems via our cfg mgmt systems but it'd be super if this, or something similar, was the default. -pete -- Pete Wright pete_at_nomadlogic.org nomadlogicLAReceived on Wed Jan 18 2017 - 17:53:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC