New answers tagged

1

As I mentioned in comment, min keystrokes are not always the most convenient. I would go with: :%s/^.*:/\U&/g Or, align all text with vim-easy-align: gaip: CTRL-V (and select all keys) U But this has a side effect of all keys aligned with :. Or without a plugin: /name gUiw j.j.j. Or with normal command: vap :'<,'>norm! wgUiw '<,'> ...


1

As you have figured out, even though a vimfiles directory isn't shipped as part of the Vim package in Cygwin, if you create one and populate it, Vim (and gVim) will use it in its search path. This is controlled by the 'runtimepath' setting. And :help 'runtimepath' confirms that the default is: Unix: "$HOME/.vim, $VIM/vimfiles, ...


0

This error occurs because the subsequent files were opened without having been actually loaded: In other words, you never switched to that buffer. So, a way of fixing this would be to cycle through all your files right as you open vim. Adding this to your .vimrc should work: " do one full loop through each file given through the commandline for _ in range(...


0

This is a speculative answer only. I suspect that gvim has its own set of fonts. Here are the unbolded, unslanted monospace fonts, manually transcribed from the selection list from :set guifont=*: Consolas Regular DejaVu Sans Mono Book Inconsolata Medium Liberation Mono Regular Lucida Console Regular Monospace Regular Source Code Pro Regular Source Code ...


0

If you are using RHEL7, it might be that you don't have gui fonts installed, especially if you started with a server. Try: # yum groupinstall fonts A lot of the responses to stack exchange threads involve something about saying that the default GVIM font looks bad if you don't have certain fonts installed. So I just installed the yum group package for ...


3

You can check if your vim runs in gui: if has("gui_running") colo koehler else colo darkblue endif You can also use gvimrc file (:h gvimrc) instead. The drawback is that you would have colorscheme run twice (one in vimrc, another in gvimrc) for gVim unless you guard it in vimrc, again, with has("gui_running"): vimrc if !has("gui_running") ...


0

From Hotschke in the comments: Please read :help load-plugins: In step (4) basically :runtime! plugin/**/*.vim happens which is before your gvimrc is sourced (step (8)) and runtimepath has been changed by vim-plug. You can remove the error by appending to your gvimrc runtime! plugin/**/*.vim. However, I recommend to use vimrc and stick to the given source ...


Top 50 recent answers are included