I recently started using VcXsrv with the hope of being able to grab text from vim (console mode) to the Windows clipboard via X11 forwarding (and the * register). It works...to an extent. As soon as I paste to Notepad, I lose the ability to yank to the Windows clipboard.I'm experiencing this issue whether I yank text to the * register directly, or use the autoselect clipboard option. (:help options (clipboard), :help guioptions_a)It doesn't appear to be tied to a specific Xserver: I've tried VcXsrv, XMing, and MobaXterm (including PuTTY w/ Moba's X Server).It doesn't appear to be tied to the terminal I'm using. I've tried PuTTY and MobaXterm.xclip can be used any number of times outside of vim with no issues.Echoing a command to xclip seems to temporarily fix the problem. I can successfully copy yank to * from vim again, but as soon as I paste to the Windows notepad, the problem is back.~/.vim/autoload and ~/.vim/plugin are empty.I use tmux regularly, but experience this problem outside of a session as well.Happens with gvim as well.My .vimrc:$ cat ~/.vimrc Default vimrc file, installed by vim spellset mouse=aset nocompatibleset backspace=indent,eol,start set autoindent set smartindentset cindentset tabstop=4set shiftwidth=4set expandtabset rulerset showcmdcolorscheme elflordsyntax enableif &term =~ ^screen  set ttymouse=xtermendiffiletype plugin onOutput of set clipboard:  clipboard=autoselect,exclude:cons\|linuxOutput of vim --version:$ vim --version | head -20VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 12 2010 02:29:33)Included patches: 1-445Modified by pkg-vim-maintainers@lists.alioth.debian.orgCompiled by jamessan@debian.orgHuge version with GTK2 GUI.  Features included (+) or not (-):+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments+cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path+float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap+menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm-mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte+multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript+printer +profile +python +quickfix +reltime +rightleft +ruby +scrollbind+signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax+tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup+X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_saveUpdate::echo @* will show the contents of the * register properly even after the bug manifests, so it appears that it's not arriving in the Windows clipboard via my X servers for some reason.
vim stops sending text to * (X11) register?
vim;x server