Neovim config
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Felix a28ff03357 Move changelog to markdown, release v1.4 3 weeks ago
after/ftplugin after: Remove unused code 3 weeks ago
autoload autoload: Uncouple plug.vim 3 weeks ago
config config: Clean up unused code, move C-U to keys.vim 3 weeks ago
ftdetect STASH state 6 months ago
ftplugin ftplugin: Delete unused code 3 weeks ago
tags stash changes 1 year ago
CHANGELOG.md Move changelog to markdown, release v1.4 3 weeks ago
README.md Update README with plugins, formatting 3 weeks ago
TUTORIAL.md Add TUTORIAL.md 3 weeks ago
init.vim init.vim: Switch back to XDG_CONFIG_HOME 3 weeks ago
vintrc.yml Update stuff 2 years ago

README.md

What?

Configuration files for neovim. Good readability, easy to extend.

Suited for German keyboard layouts (fingers rest on asdf and jklö).

Usage

  • Install neovim, make sure python is set up correctly.
  • git clone or copy files into ~/.config/nvim.
  • Download vim-plug and put plug.vim in ~/.config/nvim/autoload/.
  • Run :PlugUpdate.
  • Optional: Install things like linters (see config/)

Help

See TUTORIAL.md

Structure

Organized modularly instead of one giant vimrc for better readability.

  • init.vim loads the files from the config directory.
  • basic.vim contains some sensible defaults.
  • plugins.vim contains plugin calls.
  • colors.vim contains colorscheme settings and some fixes for ColorColumn (should work with urxvt, others untested), :Light and :Dark commands
  • keys.vim contains keybinding settings and neat functions that can be used with leader(default: comma)

The remaining files are mostly configurations and keybindings for plugins.

Credits

Plugins used:

License

The MIT License (MIT)

Copyright (c) 2020 Felix Elsner

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Addendum

Yes, I do realize the futility of maintaining a public dotfiles repo, and even writing changelogs. It feels like tending to a Zen Garden to me though.