On Sunday, July 6, 2014 5:23:39 PM UTC-7, Jacob Niehus wrote: > After patch 7.4.314, I've had characters that I hadn't typed stay on screen > even though they aren't really there and they go away after exiting insert > mode. I am using NeoComplete in Vim 7.4 with patches 1-347. The attached > patch fixes the problem without affecting the feature introduced in patch > 7.4.314. See also attached screenshots showing the current line in insert > mode and then the same line after pressing escape. That problem happens in > the current version of Vim but not after my change. > > I am seeing this problem in Cygwin (Windows 7) in both mintty and XTerm. My > Cygwin version is: > CYGWIN_NT-6.1-WOW64 1.7.30(0.272/5/3) 2014-05-23 10:36 > > Here is my Vim version information: > > VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jul 6 2014 17:07:42) > Included patches: 1-347 > Compiled by Jake@jake-mbp-win > Normal version with GTK2 GUI. Features included (+) or not (-): > +acl +clientserver -cscope -emacs_tags +folding > -keymap +menu -mouse_netterm +netbeans_intg > -python3 -sniff -tcl +virtualedit > +writebackup > -arabic +clipboard +cursorbind +eval -footer > -langmap +mksession -mouse_sgr +path_extra > +quickfix +startuptime +terminfo +visual +X11 > +autocmd +cmdline_compl +cursorshape +ex_extra +fork() > +libcall +modify_fname -mouse_sysmouse -perl > +reltime +statusline +termresponse +visualextra -xfontset > +balloon_eval +cmdline_hist +dialog_con_gui +extra_search +gettext > +linebreak +mouse -mouse_urxvt +persistent_undo > -rightleft -sun_workshop +textobjects +viminfo +xim > +browse +cmdline_info +diff -farsi > -hangul_input +lispindent +mouseshape +mouse_xterm > +postscript -ruby +syntax +title +vreplace > +xsmp_interact > +builtin_terms +comments +digraphs +file_in_path +iconv > +listcmds -mouse_dec +multi_byte +printer > +scrollbind +tag_binary +toolbar +wildignore > +xterm_clipboard > +byte_offset -conceal +dnd +find_in_path > +insert_expand +localmap -mouse_gpm +multi_lang -profile > +signs +tag_old_static +user_commands +wildmenu > -xterm_save > +cindent +cryptv -ebcdic +float +jumplist > +lua/dyn -mouse_jsbterm -mzscheme -python > +smartindent -tag_any_white +vertsplit +windows +xpm > system vimrc file: "$VIM/vimrc" > user vimrc file: "$HOME/.vimrc" > 2nd user vimrc file: "~/.vim/vimrc" > user exrc file: "$HOME/.exrc" > system gvimrc file: "$VIM/gvimrc" > user gvimrc file: "$HOME/.gvimrc" > 2nd user gvimrc file: "~/.vim/gvimrc" > system menu file: "$VIMRUNTIME/menu.vim" > fall-back for $VIM: "/home/Jake/vim_local/share/vim" > Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -D_REENTRANT > -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libpng15 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/include/freetype2 > -I/usr/include/libpng15 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 > Linking: gcc -L/usr/lib -L/usr/local/lib -Wl,--as-needed -o vim.exe > -L/usr/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -lgio-2.0 -lXinerama > -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lXfixes -latk-1.0 -lcairo -lz > -lpixman-1 -lxcb-shm -lxcb-render -lXrender -lXext -lX11 -lxcb -lXau -lXdmcp > -lgdk_pixbuf-2.0 -lm -lpng15 -lm -lz -lgio-2.0 -lz -lpangoft2-1.0 -lharfbuzz > -lpango-1.0 -lm -lgmodule-2.0 -lgobject-2.0 -lffi -lglib-2.0 -lintl -lpcre > -lintl -liconv -lpcre -lfontconfig -lexpat -lfreetype -lbz2 -lpng15 -lm -lz > -lexpat -lfreetype -lbz2 -lz -lpng15 -lm -lz -lSM -lICE -lXpm -lXt -lX11 > -lXdmcp -lSM -lICE -lm -lncurses -lelf -liconv -lintl
Bram, On further thought I don't think this patch should be included. It's a bad workaround and I have seen the completion messages pop up occasionally since using it. I'll try and find a better solution. Thanks, Jake -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
