From 3017160c462661f007e2ceb25431d1d543dfd7dc Mon Sep 17 00:00:00 2001 From: Gabe Venberg Date: Fri, 15 Mar 2024 11:52:23 -0500 Subject: [PATCH] wording changes. --- content/posts/clirenaissance/index.md | 28 +++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/content/posts/clirenaissance/index.md b/content/posts/clirenaissance/index.md index 5cf65ee..b720c2f 100644 --- a/content/posts/clirenaissance/index.md +++ b/content/posts/clirenaissance/index.md @@ -184,24 +184,24 @@ outright disabled without configuration. (for example, the earliest things I did when I first made a `.vimrc` was to enable indent folding, make some better keybinds for navigating windows, and adding a line number ruler to the side) -Neovim (bottom left) further improved on Vim, adding support for Treesitter and the Language -Server Protocoll, but the out of the box experience is the *exact* same as vim! -In order to take advantage of the LSP and Treesitter support, you have to -install plugins, which means learning a Nvim package manager, learning how to -configure LSPs, and configuring a new LSP for every language you want to use it -with. (Or finding out about Mason and being OK with having multiple levels of -package management in your Nvim install alone). Dont get me wrong, Neovim is a -great editor once you get over the hump, I still use it as my daily driver, but -so much of its functionality is simply hidden. +Neovim (bottom left) further improved on Vim, adding support for Treesitter and +the Language Server Protocoll, but the out of the box experience is the *exact* +same as vim! In order to take advantage of the LSP and Treesitter support, you +have to install plugins, which means learning a Nvim package manager, learning +how to configure LSPs, and configuring a new LSP for every language you want to +use it with. (Or finding out about Mason and being OK with having multiple +levels of package management in your Nvim install alone). Dont get me wrong, +Neovim is a great editor once you get over the hump, I still use it as my daily +driver, but so much of its functionality is simply hidden. Then we have the Helix (bottom right) editor. Colour scheme aside, everything is just there. Helix doesnt have plugin support [yet](https://github.com/helix-editor/helix/discussions/3806), but it has so much stuff in core that, looking through my neovim plugins, pretty much all of -my neovim plugins are in the core editor! (ironically, the one feature that -helix is missing, [folding](https://github.com/helix-editor/helix/issues/1840), -is a core part of neovim, albiet one that requires some configuration to get -good use out of). Helix has a config file where you can change a huge amount of +them are in the core editor! (ironically, the one feature that I feel helix is +missing, [folding](https://github.com/helix-editor/helix/issues/1840), is a core +part of neovim, albiet one that requires some configuration to get good use out +of). Helix does have a config file where you can change a huge amount of settings, but its an extremely usable IDE out of the box, thanks to having all of its features enabled by default. @@ -209,7 +209,7 @@ of its features enabled by default. -[earlier](../nushell) +[before](../nushell) ### Concise and discoverable documentation