fmouhart/blog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(nvim article): wrongly formated url + rephrasing

Browse Source
This commit is contained in:
Fabrice Mouhartem 2025-02-12 10:03:48 +01:00
parent 34f2980123
commit 30b1ce923f
Signed by: fmouhart
GPG Key ID: 2C5033B228CFE4E7
1 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
content/software/nvim-configure.md
View File

@ -1,7 +1,7 @@
---
Title: Setup Neovim with kickstart.nvim
Date: 2023-12-25 17:15
Modified: 2024-02-06 10:30
Modified: 2025-02-12 10:00
Lang: en
Author: Fabrice
Category: software
@ -24,36 +24,36 @@ there were quite a bit on conflicting keymaps as well as I'm using
[bépo](http://bepo.fr/) as my keyboard layout with [partial remaps
(fr)](https://cdn.bepo.fr/Vim-bepo-066.png).
Obviously, it slowly became quite a mess. To address this issue, I
decided to reorganise my `$HOME/.config/vim` directory using the [vim directory
structure](www.panozzaj.com/blog/2011/09/09/vim-directory-structure/) and did
some cleanup at this point of time. I think it was also around this period that
I discovered that Vim8 added a native package manager that I started to use.
Thus, at this point, I started organising my configuration with semantic files,
such as `$VIMHOME/plugin/spelling.vim` to manage my spelling configuration for
instance. This approach makes debugging easier, and also checking custom
keyboard shortcuts easier, as I just have to check
Obviously, it slowly became quite a mess. To address this issue, I decided to
reorganise my `$HOME/.config/vim` directory using the [vim directory
structure](https://www.panozzaj.com/blog/2011/09/09/vim-directory-structure/)
and did some cleanup at this point of time. I think it was also around this
period that I discovered that Vim8 added a native package manager that I started
to use. Thus, at this point, I started organising my configuration with semantic
files, such as `$VIMHOME/plugin/spelling.vim` to manage my spelling
configuration for instance. This approach makes debugging easier, and also
checking custom keyboard shortcuts easier, as I just have to check
`$VIMHOME/plugin/omnicomplete.vim` for instance to know which shortcuts I set up
when I'm still getting the habits of using them.
At some point of time, I moved to Neovim, and I simply moved my configuration
from Vim to Neovim and continue on adding more and more plugins on top of each
other depending on my hype, especially because the world of Neovim plugins
At some point of time, I moved to Neovim, and simply moved my configuration from
Vim to Neovim. All the while continuing adding more and more plugins on top of
each other depending on my hype, especially because the world of Neovim plugins
opened up to me. Needless to say that less than half of these plugins were put
into good use. Which leads to my first configuration big cleanup.
Six months ago, I wiped my frankenconfig, and started back from scratch in
Six months ago, I wiped my _frankenconfig_, and started back from scratch in
[lua](https://lua.org/about.html), with the same structural approach as
previously, but now wondering if the plugin would be useful or not. Since my
first time using Vim, there were some big changes in the vim ecosystem,
especially in language management with
[tree-sitter](https://tree-sitter.github.io/tree-sitter/) and
[lsp](https://en.wikipedia.org/wiki/Language_Server_Protocol). These two bring
into the environment a unified way to manage languages without having to depend
on language-specific plugins, henceforth I didn't need specific plugins to have
into the environment a unified way to manage languages without depending on
language-specific plugins. Henceforth, I didn't need specific plugins to have
nice syntax coloration for obscure languages anymore, or get frustrated with
[omnicomplete](https://vim.fandom.com/wiki/Omni_completion) which decided not to
work for some languages… While it's not an absolute rule (for instance, I'm
work only for some languages… While it's not an absolute rule (for instance, I'm
using [vimtex]({filename}./nvim-latex.md) for latex, which includes a more
accurate syntax coloring than tree-sitter). I also moved from the native vim way
of managing plugins to use [`Lazy`](https://github.com/folke/lazy.nvim) as a
@ -70,10 +70,10 @@ However, I was unhappy with some of my configurations, and if I managed to have
something functional, there were many details that annoy me that stemmed for
some configuration I wrote some times ago and of course didn't document. This
leads us to today, where I just decided to use
[`kickstart.nvim`](https://github.com/nvim-lua/kickstart.nvim), which is a
well-documented vim starting configuration (it's not a distribution, it still
requires your input to obtain something that fits your needs), which was exactly
what I needed to start anew… but not fully from scratch.
[`kickstart.nvim`](https://github.com/nvim-lua/kickstart.nvim). It is a well
documented vim starting configuration (it's not a distribution, it still
requires your inputs to obtain something that fits your needs), which was
exactly what I needed to start anew… but not fully from scratch.
## The migration