From 62d90435c3aee368d3a6ff593a96797fdefa3701 Mon Sep 17 00:00:00 2001 From: Fabrice Mouhartem Date: Tue, 6 Feb 2024 11:33:19 +0100 Subject: [PATCH] =?UTF-8?q?Typo:=20NVIM=5FAPP=20=E2=86=92=20NVIM=5FAPPNAME?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- content/software/nvim-configure.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/software/nvim-configure.md b/content/software/nvim-configure.md index ebb970b..087f460 100644 --- a/content/software/nvim-configure.md +++ b/content/software/nvim-configure.md @@ -1,6 +1,7 @@ --- Title: Setup Neovim with kickstart.nvim Date: 2023-12-25 17:15 +Modified: 2024-02-06 10:30 Lang: en Author: Fabrice Category: software @@ -83,10 +84,11 @@ that is over 600 lines long. I thus decided to split it into short files that manages a specific part of the configuration: completion, lsps, treesitter, mappings after reading the different configuration default from nvim-kickstart and changing what I disliked. To do that, I started with using the -[`NVIM_APP`](https://practical.li/neovim/configuration/) environment option in -order to make the move in a non-destructive way. After installing the bare -minimum to make it usable for me (as a bépo user), I exported the `NVIM_APP` -variable to start using my configuration to help me debug it on the fly. +[`NVIM_APPNAME`](https://practical.li/neovim/configuration/) environment option +in order to make the move in a non-destructive way. +After installing the bare minimum to make it usable for me (as a bépo user), I +exported the `NVIM_APPNAME` variable to start using my configuration to help me +debug it on the fly. I also decided to write this blog post to remember the process and maybe helped some people who want to configure their text editor.