After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762981 - Neovim mode change makes mouse pointer appear
Neovim mode change makes mouse pointer appear
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
git master
Other Linux
: Normal minor
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-02 12:03 UTC by Egmont Koblinger
Modified: 2017-04-16 21:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egmont Koblinger 2016-03-02 12:03:43 UTC 
In neovim (https://github.com/neovim/neovim/) change between insert and command modes ('i' and ESC).

The mouse pointer keeps re-appearing on these keypresses, although I believe it should not, it should remain hidden.
Comment 1 Egmont Koblinger 2016-03-02 12:35:10 UTC 
It keeps re-enabling mouse reporting mode \e[?1002h.

- We could ignore this if the sequence doesn't actually change the state, and not redisplay the pointer.

- Or we could change vte never redisplay the pointer when the mouse mode is toggled.

- Or we could leave it as is, and let neovim fix their code not to re-enable what's already enabled.

I have no firm opinion.
Comment 2 Christian Persch 2016-03-02 17:15:51 UTC 
Regardless of fixing neovim not to do this (which should be done anyway), I think we should do 1st option, and possibly *also* 2nd option.
Comment 3 Egmont Koblinger 2016-03-02 18:16:07 UTC 
Neovim bugreport: https://github.com/neovim/neovim/issues/4394
Comment 4 Egmont Koblinger 2016-03-02 19:04:33 UTC 
Just thinking about it... when e.g. starting up or quitting "mc" the mouse pointer appears. I got used to it, but it doesn't make too much sense, I tend to think it would be better without it. That is, I tend to vote for going for the 2nd option (which also includes the 1st).
Comment 5 Egmont Koblinger 2017-03-31 20:32:13 UTC 
See also bug 780785.
Comment 6 Egmont Koblinger 2017-04-16 21:11:39 UTC 
Fixed as part of bug 780785 comment 6.