On Sat, May 11, 2019 at 01:10:04PM +0200, Bram Moolenaar wrote:
> 
> > On Fri, May 10, 2019 at 09:57:09PM +0200, Bram Moolenaar wrote:
> > > > git bisect finds this. However I tried again and it finds 1265. Perhaps
> > > > I need to clean the workspace between each run. So I tried again and it
> > > > finds 1265 again. And reverting that patch (including 1-1264, 1266-1312)
> > > > the issue is gone.
> > > > 
> > > > Also I notice that 'set ttymouse=xterm' restores mouse support, although
> > > > it was already xterm.
> > > 
> > > Strange.  So, what is broken, how to reproduce?  Start with "vim
> > > --clean".
> > 
> > That's simple:
> > 
> > 1. be inside tmux
> > 2. vim --clean -c 'set mouse=a'
> > 
> > The mouse support is not enabled.
> > 
> > 3. :set ttymouse=xterm
> > 
> > The mouse support is now enabled.
> > 
> > tmux 2.9a running inside gnome-terminal 3.32.2 on Arch Linux.
> > 
> > This is my vim --version:
> > 
> > VIM - Vi IMproved 8.1 (2018 May 18, compiled May  7 2019 19:54:58)
> > Included patches: 1-1290
> > Huge version with GTK3 GUI.  Features included (+) or not (-):
> > +acl               +extra_search      +mouse_netterm     -tag_old_static
> > +arabic            -farsi             +mouse_sgr         -tag_any_white
> > +autocmd           +file_in_path      -mouse_sysmouse    -tcl
> > +autochdir         +find_in_path      +mouse_urxvt       +termguicolors
> > -autoservername    +float             +mouse_xterm       +terminal
> > +balloon_eval      +folding           +multi_byte        +terminfo
> > +balloon_eval_term -footer            +multi_lang        +termresponse
> > +browse            +fork()            -mzscheme          +textobjects
> > ++builtin_terms    +gettext           +netbeans_intg     +textprop
> > +byte_offset       -hangul_input      +num64             +timers
> > +channel           +iconv             +packages          +title
> > +cindent           +insert_expand     +path_extra        +toolbar
> > +clientserver      +job               +perl/dyn          +user_commands
> > +clipboard         +jumplist          +persistent_undo   +vartabs
> > +cmdline_compl     +keymap            +postscript        +vertsplit
> > +cmdline_hist      +lambda            +printer           +virtualedit
> > +cmdline_info      +langmap           +profile           +visual
> > +comments          +libcall           +python/dyn        +visualextra
> > +conceal           +linebreak         +python3/dyn       +viminfo
> > +cryptv            +lispindent        +quickfix          +vreplace
> > +cscope            +listcmds          +reltime           +wildignore
> > +cursorbind        +localmap          +rightleft         +wildmenu
> > +cursorshape       +lua/dyn           +ruby/dyn          +windows
> > +dialog_con_gui    +menu              +scrollbind        +writebackup
> > +diff              +mksession         +signs             +X11
> > +digraphs          +modify_fname      +smartindent       -xfontset
> > +dnd               +mouse             +startuptime       +xim
> > -ebcdic            +mouseshape        +statusline        -xpm
> > +emacs_tags        +mouse_dec         -sun_workshop      +xsmp_interact
> > +eval              +mouse_gpm         +syntax            +xterm_clipboard
> > +ex_extra          -mouse_jsbterm     +tag_binary        -xterm_save
> 
> I'm using the same mouse features, and for me it does not happen.
> What is $TERM set to?  It should be "screen" or "tmux".

weird. It's tmux-256color.

The following patch will fix the issue:

diff --git a/src/os_unix.c b/src/os_unix.c
index a6d1a12d1..d656e298f 100644
--- a/src/os_unix.c
+++ b/src/os_unix.c
@@ -3817,10 +3817,7 @@ check_mouse_termcode(void)
            && !gui.in_use
 #  endif
            )
-       set_mouse_termcode(KS_GPM_MOUSE,
-                                     (char_u *)IF_EB("\033MG", ESC_STR "MG"));
-    else
-       del_mouse_termcode(KS_GPM_MOUSE);
+       set_mouse_termcode(KS_MOUSE, (char_u *)IF_EB("\033MG", ESC_STR "MG"));
 # endif
 
 # ifdef FEAT_SYSMOUSE

-- 
Best regards,
lilydjwg

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190511141425.GA16637%40lilyforest.localdomain.
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui