From 64fba6c55484f12e82c1eb357a05965f438fc18d Mon Sep 17 00:00:00 2001 From: Michael James Kiernan Date: Mon, 5 Aug 2019 14:33:41 +0800 Subject: [PATCH] Updated README.md to reflect nvim path differences I've used vundle for years, and love it, thanks to everyone involved. Just setting up a new dev environment and figured I may as well capture the neovim path differences here. I'm not particularly savvy of the vim/neovim/plugin dev community, so hopefully this is a reasonable change/ isn't a faux pas of some kind. --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 07e2f143..821631a2 100644 --- a/README.md +++ b/README.md @@ -48,9 +48,13 @@ Using non-POSIX shells, such as the popular Fish shell, requires additional setup. Please check the [FAQ]. -2. Set up [Vundle]: +2. Set up [Vundle] for vim: ` git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim` + + If you are using [neovim](https://github.com/neovim/neovim), it is similarly: + + ` git clone https://github.com/VundleVim/Vundle.vim.git ~/.config/nvim/bundle/Vundle.vim` 3. Configure Plugins: @@ -61,7 +65,7 @@ filetype off " required " set the runtime path to include Vundle and initialize - set rtp+=~/.vim/bundle/Vundle.vim + set rtp+=~/.vim/bundle/Vundle.vim " neovim variant: set rtp+=~/.config/nvim/bundle/Vundle.vim call vundle#begin() " alternatively, pass a path where Vundle should install plugins "call vundle#begin('~/some/path/here')