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.
5 Commits
1 Branch
0 Tags
155 KiB
Vim script 100%
 
Go to file
Jef Roosens aa00a2dcae Updated gitignore 2020-08-17 09:57:35 +02:00
autoload Initial commit 2020-08-08 20:27:01 +02:00
colors Initial commit 2020-08-08 20:27:01 +02:00
ftplugin Autogroups n stuff 2020-08-17 09:55:58 +02:00
init Autogroups n stuff 2020-08-17 09:55:58 +02:00
.gitignore Updated gitignore 2020-08-17 09:57:35 +02:00
.netrwhist Autogroups n stuff 2020-08-17 09:55:58 +02:00
README.md Autogroups n stuff 2020-08-17 09:55:58 +02:00
coc-settings.json Initial commit 2020-08-08 20:27:01 +02:00
init.vim Added more hard way config 2020-08-09 07:49:51 +02:00

README.md

My Neovim Config

Intro

Neovim, the popular fork of the original Vim, has been my main text editor for a few months. Over this time, I've made lots of changes to the config. The goal of this repository is to be an advanced config that's still very much readable. I've commented as much as I can, and I try to explain as many vague/difficult settings as possible.

Goals

When I started to config my Neovim, I had a few goals in mind:

  • Only use key bindings that use buttons available on any keyboard:
    • letter keys
    • spacebar
    • backspace
  • Make the config work the same on QWERTY and AZERTY (French keyboard layout)
  • Leave the homerow as little as possible (no uncomfortable stretching)
  • Make it ready for any language that I need to write for college and/or personal projects.

Design

I like to split my configs up into multiple files, as you can see in this repository. It makes it easier for me to navigate, and it makes it so I don't just have a file that's a thousand lines long.