Skip to content

tony/vim-config-framework

Repository files navigation

Lessons from having a complex vim config: don't do it

It's a time sink.

Having the vim configuration break all the time, and pasting in "nice to have" stuff has caused me more disruption / harm than it has benefitted me. I'm trying to turn my VIM into a lean editing system, and just learning plain-old VIM more effectively.

If you want to go back to where I used to be to look feel free to see: https://github.com/tony/vim-config-framework/tree/2018-06-09

I'm hoping to have a happier, healthier VIM experience, life, etc. with a simple vim config.

Plugin Architecture

This configuration implements an auto-installing, gracefully degrading plugin system built on vim-plug:

  • Auto-Installation: Automatically bootstraps vim-plug and installs plugins on first run
  • Graceful Degradation: Conditionally loads plugins based on available executables and features
  • Modular Design: Supports local customizations through plugins.d/ and plugins.settings/ directories
  • Progressive Enhancement: Basic functionality always works, advanced features added when dependencies exist

See notes/analysis.md for detailed architecture analysis.

Please check out:

License

MIT

Vendorizes sensible.vim, see license permission.

About

📗 VIM / Neovim configuration framework

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •