nickspoons
commented
3 years ago I'm not sure what you mean. I tried using your minimal config and it seems to work similarly to this, with my normal config:
Can you share a screencast of the problem?
Closed rcmosher closed 2 years ago
nickspoons
commented
3 years ago I'm not sure what you mean. I tried using your minimal config and it seems to work similarly to this, with my normal config:
Can you share a screencast of the problem?
rcmosher
commented
3 years ago 
nickspoons
commented
3 years ago I can't reproduce this.
I've tried with a clean ~/.vim dir containing only a freshly cloned omnisharp-vim and ALE in the ~/.vim/plugged dir, and ~/.vim/autoload/plug.vim and ~/.vim/vimrc containing your example.
nickspoons
commented
3 years ago 
rcmosher
commented
3 years ago Odd. I created a new user to make sure I had a fresh start and can still reproduce the behavior. Let me know if any more info would be useful.
Demoing started with a clean ~/.vim dir. Also that :s/\%V... works, so it is just a visual issue.
vim --version # on my linux machine, but it's roughly the same in WSL
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 27 2021 18:57:19) Included patches: 1-2815 Modified by jonathon.fernyhough@york.ac.uk Compiled by jonathon.fernyhough@york.ac.uk Huge version with GTK3 GUI. Features included (+) or not (-): +acl -farsi +mouse_sgr +tag_binary +arabic +file_in_path -mouse_sysmouse -tag_old_static +autocmd +find_in_path +mouse_urxvt -tag_any_white +autochdir +float +mouse_xterm +tcl -autoservername +folding +multi_byte +termguicolors +balloon_eval -footer +multi_lang +terminal +balloon_eval_term +fork() -mzscheme +terminfo +browse +gettext +netbeans_intg +termresponse ++builtin_terms -hangul_input +num64 +textobjects +byte_offset +iconv +packages +textprop +channel +insert_expand +path_extra +timers +cindent +ipv6 +perl +title +clientserver +job +persistent_undo +toolbar +clipboard +jumplist +popupwin +user_commands +cmdline_compl +keymap +postscript +vartabs +cmdline_hist +lambda +printer +vertsplit +cmdline_info +langmap +profile +virtualedit +comments +libcall -python +visual +conceal +linebreak +python3 +visualextra +cryptv +lispindent +quickfix +viminfo +cscope +listcmds +reltime +vreplace +cursorbind +localmap +rightleft +wildignore +cursorshape +lua +ruby +wildmenu +dialog_con_gui +menu +scrollbind +windows +diff +mksession +signs +writebackup +digraphs +modify_fname +smartindent +X11 +dnd +mouse +sound -xfontset -ebcdic +mouseshape +spell +xim +emacs_tags +mouse_dec +startuptime +xpm +eval +mouse_gpm +statusline +xsmp_interact +ex_extra -mouse_jsbterm -sun_workshop +xterm_clipboard +extra_search +mouse_netterm +syntax -xterm_save 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" defaults file: "$VIMRUNTIME/defaults.vim" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -g -O2 -fdebug-prefix-map=/build/vim-hllSLN/vim-8.2.2815=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lselinux -lcanberra -lacl -lattr -lgpm -ldl -L/usr/lib -llua5.2 -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/perl/5.30/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/python3.8/config-3.8-x86_64-linux-gnu -lpython3.8 -lcrypt -lpthread -ldl -lutil -lm -lm -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lm -lruby-2.7 -lm -L/usr/lib
nickspoons
commented
2 years ago Closing, as I was never able to reproduce the issue, and the asciinema screencasts have now been archived.
Feel free to re-open if there are more repro steps available
This is a minor bug. When selecting some text in visual mode and then typing
:to enter ex/command-line mode the highlighting of the selection disappears. I don't think it actually affects functionality (I originally thought it did, but ex mode is always linewise, even if you entered it from non-linewise visual mode).I've reproduce in Vim 8.2 in both Linux and WSL. I've narrowed it down to Omnisharp-vim by using the following vimrc.
Note, this does happen without ale, but only when entering visual mode before syntax highlighting is updated with Omnisharp customization. However, using ale the issue persists throughout a vim session. Also, if you initially edit a filetype not handled by Omnisharp, the issue doesn't occur. But once a file handled by Omnisharp is opened it happens in all buffers regardless of filetype.