[vim/vim] Disable auto visual mode on when double-clicking mouse (Issue #10094)

281 views
Skip to first unread message

Yudi Zhou

unread,
Apr 5, 2022, 8:29:09 PM4/5/22
to vim/vim, Subscribed

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
If you double click mouse on any text, the vim automatically switch to visual mode. This can cause a lot of frustration such as random highlighting bunch of text when you start navigating the doc or preventing correct highlighting during search.

This design is very anti-pattern. Intiutively, no one would anticipate a mode switch and they start run into annoying random higlighting and other stuff. It brings more disruption and confusion than its functionality.

Describe the solution you'd like
Simply disable this auto-enable visual mode would solve a lot of headache.

Describe alternatives you've considered
When customers double clicking on words, or perform any other mouse events, Vim will stay in the existing mode.
Customer can opt-in to enable auto switch by configuring set mouse setting.


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10094@github.com>

Bram Moolenaar

unread,
Apr 6, 2022, 5:54:21 AM4/6/22
to vim/vim, Subscribed

I find the double click to select a word very convenient.
If you don't want it, you can use this:

:map <2-LeftMouse> <Nop>
:map! <2-LeftMouse> <Nop>


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10094/1090079060@github.com>

Bram Moolenaar

unread,
Apr 6, 2022, 5:54:26 AM4/6/22
to vim/vim, Subscribed

Closed #10094.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/10094/issue_event/6378703168@github.com>

Yudi Zhou

unread,
Apr 6, 2022, 4:02:29 PM4/6/22
to vim/vim, Subscribed

Good ot see there is a workaround. It works for my use case.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/10094/1090720364@github.com>

Reply all
Reply to author
Forward
0 new messages