PageRenderTime 67ms CodeModel.GetById 22ms RepoModel.GetById 1ms app.codeStats 0ms

/README.markdown

https://github.com/jperras/vim-dotfiles
Markdown | 72 lines | 54 code | 18 blank | 0 comment | 0 complexity | 86af007219b0380477a53e55f19f3b4b MD5 | raw file
  1. ## The Dotfiles
  2. These are the Vim runtime files that I use on a daily basis. Feel free to
  3. clone, modify, change, add, murder or remove portions of it at will.
  4. Note that I actually use [NeoVim](https://github.com/neovim/neovim), and have
  5. been doing so for quite some time now without any compatibility issues.
  6. I used to be a heavy advocate and user of
  7. [Pathogen](https://github.com/tpope/vim-pathogen) by the most excellent Tim
  8. Pope, then I switched to
  9. [Vundle](https://github.com/gmarik/vundle) because I got tired of futzing
  10. around with git submodules every time I wanted to update or remove
  11. a bundle. About a year after using and liking Vundle, I began using neovim
  12. in earnest, and found that it was stable enough for my day-to-day usage.
  13. Due to some underlying work in neovim,
  14. [vim-plug](https://github.com/junegunn/vim-plug) is able to take advantage
  15. of some parallel execution of installs/updates of the underlying git
  16. repositories that make up the collection of plugins, among other several
  17. other nice features that are listed in the
  18. [README](https://github.com/junegunn/vim-plug/blob/master/README.md).
  19. ## Usage
  20. **NOTE**: If you have existing files in `$HOME/.vim`, `$HOME/.vimrc`,or
  21. the neovim equivalents `$HOME/.nvim` and `$HOME/.nvimrc`, make sure you
  22. take appropriate backups before performing any of the following steps.
  23. - First install Vim-Plug, as per their
  24. [instructions](https://github.com/junegunn/vim-plug#installation):
  25. ```sh
  26. curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
  27. https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  28. ```
  29. > Change the destination to `~/.nvim/autoload/plug.vim` in the above if
  30. > you're using NeoVim, of course. This applies to all steps.
  31. - Next, get my vim-dotfiles & symlink the `.vimrc` to your `$HOME/.vimrc`:
  32. ```sh
  33. $ git clone git@github.com:jperras/vim-dotfiles.git ~/.vim && ln -s ~/.vim/.vimrc ~/.vimrc
  34. ```
  35. - There are several extensions required to make some extensions function
  36. correctly. You'll need to install the following to your system:
  37. * [*fzf*](https://github.com/junegunn/fzf): For the best fuzzy file-finding you'll ever use.
  38. * *ctags*: For the tagbar functionality.
  39. * [*ripgrep*](https://github.com/BurntSushi/ripgrep): For a better grep.
  40. * [*neovim-python*](https://github.com/neovim/python-client): The python client for neovim plugins.
  41. * [*flake8*](https://pypi.python.org/pypi/flake8): For Python syntax & PEP8 validation via Neomake.
  42. - Finally, we need to launch Vim and then invoke the appropriate Vim-Plug
  43. commands to install all of the bundles using the `:PlugInstall`
  44. command.
  45. And that's it! Be sure to source your newly installed configuration (`:source
  46. $MYVIMRC` from inside Vim, or just restart a new editor session), and you
  47. should be good to go.
  48. The included `.vimrc` contains some very minimal configurations that should be
  49. sane defaults for most developers. Feel free to modify at will, of course. See the
  50. comments in the `.vimrc` file for more details, and check out the individual
  51. bundles that are pulled in on github until I decide to annotate & comment on
  52. what each of them do.
  53. ## Screenshot
  54. And here's a gratuitous screenshot using an iTerm2 window, a few (n)Vim split panes, and the gruvbox colorscheme: ![screenshot](http://snaps.nerderati.com/wNTqkSPH.png)