- vimrc
- gvimrc
- init.lua
- obsidian.vimrc
- vim-plug glob
- source code pro font (tff) - for gvimrc
- A Good Vimrc
- Minimal Vim Configuration With vim-plug: For A Barebones Starter Config - devel.tech
- GitHub - junegunn/vim-plug: Minimalist Vim Plugin Manager
- How I boosted my Vim » nvie.com
- Vim 101: Set Hidden – usevim – Medium
- Vim for Writers - NaperWriMo Wiki
- "Vim Side Search: Making Search Fun Again"
- The Last Statusline For Vim – Hacker Noon
- Why I love Vim: It’s the lesser-known features that make it so amazing
- Learn Vimscript the Hard Way
- a guide to LSP in vim
- How I Vim - interviews
- Vimcasts - Free screencasts about the text editor Vim
- usevim – Medium
- How I Take Notes With Vim, Markdown, and Pandoc - things james does
- Building vim from source
- ripgrep is faster than {grep, ag, git grep, ucg, pt, sift} - Andrew Gallant's Blog
- GitHub - bchretien/vim-profiler: Utility script to profile (n)vim (e.g. startup times of plugins)
- TabNine | Deep Learning for code completion - freemium
- Improving Vim Workflow With fzf | Pragmatic Pineapple
- How to copy text from vim to system clipboard? · Issue #892 · microsoft/WSL · GitHub
- Tmux and Vim — configurations to be better together | BugSnag Blog
- LSP | Langserver.org
- Do LSP's make tag generating tools obsolete?
- Why do Vim experts prefer buffers over tabs? - Stack Overflow
- A LSP client maintainer's view of the protocol | YCM
- GitHub - MordechaiHadad/bob: A version manager for neovim
- GitHub - akrawchyk/awesome-vim: The Vim plugin shortlist
- Vim Awesome
- Dotfyle | Neovim Plugin Search | Neovim Config Search | Neovim News
- rockerBOO/awesome-neovim: Collections of awesome neovim plugins.
- nvimawesome
- Modules labeled 'neovim' - LuaRocks
- neovimcraft
- Vim Tips Wiki | Fandom
- when using airblade/vim-rooter: Changes Vim working directory to project root.( https://github.com/airblade/vim-rooter ) - doesn't work well with nerdtree because it unsets
autochdirand because of that, I can't open NerdTree in the VCS root on vim start.
I started with vim but now, I'm using neovim... the config has bloated quite a bit and its compatibility with vim may have been broken. At some point, I might have to split the config for vim and neovim exclusive.
This part is mostly done now. I already ended up splitting plugin stuff for vim and nvim, while keeping the common settings shared. So this is not really a TODO anymore, more like the reasons why nvim support got added here in the first place.
As for reasons (excuses) for migration away from vim towards nvim:
- nvim has tree-sitter support through
nvim-treesitter. native lua support. Nvim has built-in Lua support. Latest Vim also has a Lua interface when built with+lua(REF: regular Vim has lua?! | r/neovim)- nvim has
:checkhealth, which is useful when plugins or external tools stop working. more robust async support. Nvim has a proper API/RPC surface. Latest Vim also has jobs, channels, andlsp/dapchannel modes.- nvim has a native LSP client in core.
- dap support is better for me in practice. Vim now has DAP protocol plumbing in channels, but that is not the same as a builtin debug client. See the DAP spec.
embedded terminal support. Nvim has a terminal. Latest Vim also has terminal windows.floating windows / popup kind of UI. Latest Vim also has popup windows.- file change detection was another reason i kept leaning nvim way back then; see this old nvim issue. In Vim I had to use workarounds like this.
- nvim can be embedded into other editors through things like vscode-neovim and firenvim.
- Lua plugins and user config fit nvim more naturally because Lua is part of the runtime model.
- Biggest of all, vim could have only vim plugins, nvim can have both vim and nvim plugins. (although i haven't tried with the optional lua support in vim)
A few of these did eventually find its ways to vim too. but for this config, nvim still seems better imo. but, given i spent too much time configuring vim, i'm still keeping the vim config around (sunk cost maybe?).