Chewing_Bever
/
neovim-config
Archived
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Moved to my dotfiles repo.
This repository has been archived on 2021-12-21. You can view files and clone it, but cannot push or open issues/pull-requests.
24 Commits
1 Branch
0 Tags
155 KiB
Vim script 100%
 
Go to file
Jef Roosens a5dcb6a0e2 Added leader part 2021-02-01 10:10:38 +01:00
autoload Added all new files 2021-02-01 09:41:32 +01:00
colors Added tokyonight colorscheme 2020-10-23 09:54:33 +02:00
ftplugin Added all new files 2021-02-01 09:41:32 +01:00
init Started main README 2021-02-01 09:59:11 +01:00
.gitignore Added all new files 2021-02-01 09:41:32 +01:00
LICENSE Initial commit 2021-02-01 08:36:59 +00:00
README.md Added leader part 2021-02-01 10:10:38 +01:00
coc-settings.json Added all new files 2021-02-01 09:41:32 +01:00
coc-settings.json.back Added all new files 2021-02-01 09:41:32 +01:00
init.vim Moved plugins config to separate dir 2021-02-01 09:48:09 +01:00

README.md

neovim-config

This repo contains the full Neovim config that I use on a daily basis for college and personal projects.

Config structure

The config exists of a few key components:

  • coc-settings.json: config for the CoC plugin.
  • init.vim: this is the actual config file that gets loaded. It sources everything else.
  • autoload/: a special directory allowing the files inside to be used in the :call command. Its only use is allowing usage of vim-plug, my plugin manager.
  • colors/: contains my themes.
  • ftplugin/: this is where you can put filetype plugins. These are vim scripts that are sourced whenever you open a buffer with the given filetype, e.g. if you open a file with filetype markdown, it will source the file ftplugin/markdown.vim, if it exists. This allows for custom configs for certain filetypes.
  • init/: contains the various config files sourced by init.vim. I could just cram it all into a single file, but I find this difficult to maintain.

Choice of leader

In my opinion, an important part of any (Neo)vim config is choosing which leader key to use. The default \ leader wasn't going to cut it for me for three main reasons:

  • Backslash required me to stretch my hand every time
  • In Belgium (where I live), we use AZERTY instead of QWERTY, and the backslash key is often not present on those keyboards or requires a key combination to type
  • I use both AZERTY and QWERTY and wanted a key that was the same on both

Therefore, I chose Space as my main leader key and Tab as my local leader (even though I've never actually used it). This allows me to use the same muscle memory on my refurbished MacBook (AZERTY) and my Ducky (QWERTY).