/explore
|
You are here 
|
xnacly.me | ||
| | | | |
ncona.com
I've known about neovim for a long time, but I've never tried it out. My goal for this article is to try to replicate my current vim configuration: File explorer Grep Fuzzy file finder Syntax highlight .vimrc configuration If Neovim is as good as people say, I should be able to do that, and it should run faster. Installation Neovim is already packaged for most OS. Sadly, the version included in Ubuntu is too old for most plugins out there. For this reason, we'll have to build from source. Install prerequisites: 1 sudo apt-get install ninja-build gettext cmake unzip curl |
|
| | | | | ||
| | | | |
nickjanetakis.com
There may come a time where you want to set a few different types of files to a specific file type for better editor support. |
|
| | | | | ||
| | | | |
www.integralist.co.uk
UPDATE November 2022 Not long after I wrote this post I had switched from VimScript to using Lua and also making large sets of changes and tweaks to my configuration. The source of truth is: https://github.com/integralist/nvim (which is a submodule within https://github.com/integralist/dotfiles) This post is being kept for posterity, but ultimately I would recommend you look at the above dotfiles repo instead. This is going to be a very focused post because when you're looking to get your code editor con... |
|
| | | | | ||
| | | | |
coen.needell.org
Vim, "the ubiquitous text editor", has been with us since the 1980s, with new programmers discovering its arcane power every day. It was originally developed for the Atari ST under the name "Stevie" (ST Editor for VI Enthusiasts), and was later ported to Unix and OS/2 (a precursor to Windows). Originally, vim was simply an Atari port of vi1:, which in turn was the visual mode for the command line text editor ex2. It continued to use the name "Stevie" until 1993, when the name was changed to Vi iMproved (... |
|
| | | |||
