You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using urxvt / rxvt-unicode as a terminal, and have set mouse=a.
When I want to select text from the terminal window, I use "Shift" while clicking and dragging the text (or double-clicking it).
With Neovim, this can trigger/start the visual mode, while it gets ignored correctly by vanilla Vim. This appears to only happen after the mouse has been used once to trigger the visual mode.
In this case both Neovim and rxvt-unicode appear to manage their selections - the issue is not that just visual mode is started (as if Shift wasn't used).
TEST CASE:
nvim -u NONE
:set mouse=a
use the mouse to start visual mode (click and drag)
Escape
Use the mouse with Shift pressed to select text
Using "Shift-mouse" before visual mode is being triggered through the mouse works.
It's not a problem with gnome-terminal.
Visual mode should not get triggered again, but it is.
The text was updated successfully, but these errors were encountered:
Without this shifted mouse-dragging would be reported to the app (via
1002 in DECSET).
This makes Neovim start visual selection for example.
Fixesneovim/neovim#2520.
I am using urxvt / rxvt-unicode as a terminal, and have
set mouse=a
.When I want to select text from the terminal window, I use "Shift" while clicking and dragging the text (or double-clicking it).
With Neovim, this can trigger/start the visual mode, while it gets ignored correctly by vanilla Vim. This appears to only happen after the mouse has been used once to trigger the visual mode.
In this case both Neovim and rxvt-unicode appear to manage their selections - the issue is not that just visual mode is started (as if Shift wasn't used).
TEST CASE:
nvim -u NONE
Using "Shift-mouse" before visual mode is being triggered through the mouse works.
It's not a problem with gnome-terminal.
Visual mode should not get triggered again, but it is.
The text was updated successfully, but these errors were encountered: