Chewing_Bever
/
neovim-config
Archived
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added leader part

master
Jef Roosens 2021-02-01 10:10:38 +01:00
parent acbf6a126c
commit a5dcb6a0e2
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -7,9 +7,9 @@ college and personal projects.
The config exists of a few key components: The config exists of a few key components:
* `coc-settings.json`: config for the * `coc-settings.json`: config for the
[CoC](https://github.com/neoclide/coc.nvim) plugin.
* `init.vim`: this is the actual config file that gets loaded. It sources * `init.vim`: this is the actual config file that gets loaded. It sources
everything else. everything else.
[CoC](https://github.com/neoclide/coc.nvim) plugin.
* `autoload/`: a special directory allowing the files inside to be used in the * `autoload/`: a special directory allowing the files inside to be used in the
`:call` command. Its only use is allowing usage of `:call` command. Its only use is allowing usage of
[vim-plug](https://github.com/junegunn/vim-plug), my plugin manager. [vim-plug](https://github.com/junegunn/vim-plug), my plugin manager.
@ -21,3 +21,18 @@ The config exists of a few key components:
certain filetypes. certain filetypes.
* `init/`: contains the various config files sourced by `init.vim`. I could * `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. 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).