From 80a0e92e1833568e8b97b5fb46ded6f9d6861787 Mon Sep 17 00:00:00 2001 From: WJH Date: Wed, 28 Oct 2020 21:28:19 +0800 Subject: [PATCH] For more info, please refer to https://github.com/vim-airline/vim-airline/issues/2264 --- ...ommand-compatible-to-other-extensions-such-as-Vim-Airline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename Installation.md => fix:-make-installation-command-compatible-to-other-extensions-such-as-Vim-Airline.md (89%) diff --git a/Installation.md b/fix:-make-installation-command-compatible-to-other-extensions-such-as-Vim-Airline.md similarity index 89% rename from Installation.md rename to fix:-make-installation-command-compatible-to-other-extensions-such-as-Vim-Airline.md index 763d96b..39086e2 100644 --- a/Installation.md +++ b/fix:-make-installation-command-compatible-to-other-extensions-such-as-Vim-Airline.md @@ -14,7 +14,7 @@ First of all let's start with basics. Pick your favorite plugin manager: [Pathog + `git clone https://github.com/morhetz/gruvbox.git ~/.vim/pack/default/start/gruvbox` -Then add the line `autocmd vimenter * colorscheme gruvbox` to your .vimrc file, and restart vim. If you are using a plugin manager like Vundle, make sure this setting is after the plugin initialization section. +Then add the line `autocmd vimenter * ++nested colorscheme gruvbox` to your .vimrc file, and restart vim. If you are using a plugin manager like Vundle, make sure this setting is after the plugin initialization section. [the reason we are using autocmd is that, vim always read .vimrc file first and after that starts to load plugins, so in this case, we use autocmd vimenter, to be sure that all plugins are loaded completely and then use gruvbox] If you're using GUI version of vim that should be enough. Otherwise let me guide you through the hell of [terminal specific issues](https://github.com/morhetz/gruvbox/wiki/Terminal-specific).