2023-12-25 19:54:41 +01:00
|
|
|
In this repository lies my Neovim configuration starting from
|
2023-12-24 11:30:17 +01:00
|
|
|
[kickstart.nvim](https://github.com/nvim-lua/kickstart.nvim).
|
|
|
|
|
2024-04-17 09:40:25 +02:00
|
|
|
The provided `init.lua` file has then been split into (tentatively) semantically
|
2023-12-24 11:32:24 +01:00
|
|
|
consistent files inside `lua/` and personal customizations have been applied.
|
2023-12-24 11:53:58 +01:00
|
|
|
|
2024-11-10 15:23:11 +01:00
|
|
|
The process to design this configuration and some thoughts can be found
|
|
|
|
[here](https://blog.epheme.re/software/nvim-kickstart.html).
|
|
|
|
|
2025-02-11 09:47:11 +01:00
|
|
|
Note that if the global principles remain true, the blog post dates from
|
|
|
|
december 2023, and things may have changed a bit since then. Just use it as a
|
|
|
|
reference for my rationals.
|
2023-12-25 19:54:41 +01:00
|
|
|
|
2023-12-24 11:54:25 +01:00
|
|
|
## Testing it
|
2023-12-24 11:53:58 +01:00
|
|
|
|
|
|
|
To try it, you can use the `NVIM_APPNAME` environment variable:
|
|
|
|
- [Practicalii Neovim: Neovim Configuration](https://practical.li/neovim/configuration/)
|
|
|
|
|
|
|
|
For instance, you can create clone this repository inside
|
|
|
|
`$HOME/.config/kicknvim` and then add to your shell configuration:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
export NVIM_APPNAME="$HOME/.config/kicknvim"
|
|
|
|
```
|