wording changes.
This commit is contained in:
		
							parent
							
								
									18c969f56a
								
							
						
					
					
						commit
						3017160c46
					
				
					 1 changed files with 14 additions and 14 deletions
				
			
		| 
						 | 
				
			
			@ -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.
 | 
			
		|||
 | 
			
		||||
<!-- look at nushells error messages-->
 | 
			
		||||
 | 
			
		||||
[earlier](../nushell)
 | 
			
		||||
[before](../nushell)
 | 
			
		||||
 | 
			
		||||
### Concise and discoverable documentation
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue