On upgrading to the latest version of Vim, I noticed that starting Vim up
results in a Vim session that doesn't respond to mouse clicks (cursor looks like
"I"). I'd appreciate it if someone else could reproduce this error.
Out put ":version"...
VIM - Vi IMproved 8.1 (2018 May 17, compiled May 24 2018 09:52:50)
Included patches: 1-22
Compiled by Jason Franklin
Huge version without GUI. Features included (+) or not (-):
+acl +cmdline_compl -ebcdic -hangul_input
-lua +mouse_xterm -python +tag_binary
+vertsplit -xpm
+arabic +cmdline_hist +emacs_tags +iconv
+menu +multi_byte -python3 +tag_old_static
+virtualedit -xsmp
+autocmd +cmdline_info +eval +insert_expand
+mksession +multi_lang +quickfix -tag_any_white
+visual -xterm_clipboard
-autoservername +comments +ex_extra +job
+modify_fname -mzscheme +reltime -tcl
+visualextra -xterm_save
-balloon_eval +conceal +extra_search +jumplist
+mouse +netbeans_intg +rightleft +termguicolors
+viminfo
+balloon_eval_term +cryptv +farsi +keymap
-mouseshape +num64 -ruby +terminal
+vreplace
-browse +cscope +file_in_path +lambda
+mouse_dec +packages +scrollbind +terminfo
+wildignore
++builtin_terms +cursorbind +find_in_path +langmap
-mouse_gpm +path_extra +signs +termresponse
+wildmenu
+byte_offset +cursorshape +float +libcall
-mouse_jsbterm -perl +smartindent +textobjects
+windows
+channel +dialog_con +folding +linebreak
+mouse_netterm +persistent_undo +startuptime +timers
+writebackup
+cindent +diff -footer +lispindent
+mouse_sgr +postscript +statusline +title -X11
-clientserver +digraphs +fork() +listcmds
-mouse_sysmouse +printer -sun_workshop -toolbar
-xfontset
-clipboard -dnd +gettext +localmap
+mouse_urxvt +profile +syntax +user_commands -xim
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -std=gnu99 -c -I. -Iproto -DHAVE_CONFIG_H -g -O0
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -std=gnu99 -L/usr/local/lib -Wl,--as-needed -o vim -lSM -lICE
-lm -ltinfo -lelf -lnsl -lselinux -lacl -lattr
The simplest possible vimrc I can create that will replicate the bug is:
set nocp
set mouse=a
set balloonevalterm
If I comment out either the first line or the last line, the bug goes away.
--
--
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].
For more options, visit https://groups.google.com/d/optout.