/explore
|
You are here 
|
www.devas.life | ||
| | | | |
dusty.phillips.codes
|
|
| | | | | Throughout my career, Ive at least tried most of the available programming editors. More than two decades ago, I heard about the vi-vs-emacs debate, and made a pact with myself to use both for at least a year before deciding which I preferred. I started with vim, switched to emacs after a year, and decided I preferred vim. I joined the sublime-text bandwagon for a year or two in the early 2010s, switched back to vim in the middle of the decade, and eventually did the big switch to vscode. | |
| | | | |
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 (... | |
| | | | |
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 | |
| | | | |
whitep4nth3r.com
|
|
| | | Learn how to build, test and release a JavaScript node module in ES6 all the way from npm init to npm publish. | ||
