Skip to content

GLaDOS-418/vim

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

(n)vim config

CONTENTS

  • vimrc
  • gvimrc
  • init.lua
  • obsidian.vimrc
  • vim-plug glob
  • source code pro font (tff) - for gvimrc

SOURCE

USEFUL LINKS

DISCUSSIONS

IMPROVE VIM

SOCIAL MEDIA

WIP

KNOWN ISSUES

  • 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 autochdir and because of that, I can't open NerdTree in the VCS root on vim start.

TODO

right now there's an attempt to keep the config compatible with both vim and neovim. Although, I might move completely to neovim and put vim config in archive mode or maybe i'll restructure my config to separate vim/neovim/vscode-nvim config.

As of Aug 2023, after Bram Moolenaar's passing, vim's future is yet to be seen. vim was already an improvement over vi and neovim is an attempt to improve upon that.

neovim has tree-sitter support, native lua support, more exclusive plugins, client-server architecture, community driven, better out-of-the-box config, several other optimisations (e.g. better file change detection (you can use this workaround ) ), it has an inbuilt library 'Checkhealth' to see if everything's installed properly or not.

You can embed nvim into other editors (e.g. vscode-neovim, firenvim ), no more half-baked vim emulations and more work is being done on this and more. the nvim code is being refactored to move away from vimscript one part at a time to lua and it's a fast moving project.

nvim was moving ahead of vim development in terms of new features. it has more robust async support (RPC API), native lsp support and a better dap support, embedded terminal support, floating windows etc. a few of which eventually found its ways to vim but, apparently nvim does them better.