/explore
|
You are here 
|
hackingcpp.com | ||
| | | | |
blog.langworth.com
My earlier posts about using Vim were well received and it's about time for an update. I've been doing a lot more work with Vim lately and have spent some time configuring my workflow for peak efficiency, so here's a snapshot of my current state. |
|
| | | | | ||
| | | | |
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 |
|
| | | | | ||
| | | | |
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 (... |
|
| | | | | ||
| | | | |
cyberchris.xyz
Intro So after picking up Vim less than a year ago, and spending a lot of time with it, I can say for sure it is the best text editor I have ever used. Okay, that's all the Vim propaganda you'll find in this post. The main aim of this post is to get people new to Vim into a comfortable environment, while also teaching you how to get plugins into your vim config since you'll probably want to customize it, once you get a feel of Vim. |
|
| | | |||
