Vim Icon


Vim is a console-run text editor program.
43 Stories
All Topics

The Changelog The Changelog #457

Why Neovim?

This week Neovim core maintainer TJ DeVries joins Jerod and guest co-host Nick Nisi (from JS Party) to follow-up on our Vim episode with a conversation dedicated to Neovim. TJ tells us why Neovim was created in the first place, how it differs from Vim, why Lua is awesome for configuration and plugins, what LSPs are all about, the cool tech inside tree-sitter, and how he’s writing his own fuzzy file finder for Neovim called Telescope.

Jerod Santo YouTube

Vimming with Nick Nisi

We had a lot of fun recording the Vim with me series alongside episode 450, so I thought, “Hey, let’s keep it going!” We have Nick Nisi for you today. Nick is a regular panelist on JS Party, co-hosted our upcoming Neovim episode of The Changelog, and is personally responsible for the #vimparty channel of Changelog’s community Slack.

(If you have any requests of people you’d like to see Vimming with me, let us know in the comments!)

Nikola Đuza

Improving your Vim workflow with fzf

Did you know that this fuzzy finder - fzf, can do a lot more than you thought? Oh yeah, the fuzzy search is just the tip of the iceberg here. It is like wine; the more you leave it on your computer, the more flavor and sweetness it accumulates from that command-line. Let’s dive in and find out how you can increase your productivity with fzf inside Vim.


A Neovim plugin that lets you write your .vimrc in Lua

Vimpeccable is a plugin for Neovim that allows you to easily replace your vimscript-based .vimrc with a lua-based one instead. Vimpeccable adds to the existing Neovim lua API by adding new lua commands to easily map keys directly to lua.

All of the power and customization of Vim without the inscrutable and othewise compulsory Vimscript? Sign me up! (metaphorically… I’m far too lazy to customize Vim anymore than I already have.)

Nikola Đuza

Why learn Vim in 2020?

Nikola Đuza makes a compelling case for the powerful text editor that developers love (or love to hate):

What Vim is excellent at is navigating, making some changes, and repeating the process. The process most call editing (not to be confused with writing). Most developers tend to overlook this fact, but this is one of the strong selling points of Vim. Developers are more prone to reading code, jumping from file to file, making small incisions in the code, and writing code all the time.


A new interactive finder and dispatcher for Vim and Neovim

Vim-clap is different than previous finders because it uses the new floating_win (NeoVim) and popup (Vim) interface. File lookup and switching have long been what keep me out of Vim as my daily driver (clunky UIs, slow results). Nothing beats Sublime Text in this category, in my opinion.

But this looks pretty awesome. I might have to give this a test drive and see if it wins me back.

A new interactive finder and dispatcher for Vim and Neovim

Thoughtbot Icon Thoughtbot

Profiling Vim

Chris Thorn writing for Thoughtbot:

Lately, I’ve noticed that opening Markdown files in Vim is slow. I don’t know exactly how slow, but slow enough that I notice a pause after opening the file before I can edit it. I’m not sure why or when it started, but it’s painful enough that I want to track down and alleviate it.

I, too, have felt this pain, which is one of the reasons I no longer use Vim as my full-time coding editor. I still use it enough for its sluggishness to bug me, but not quite enough to go chasing down why it’s sluggish. This article might change my calculus on that decision.

Omer Hamerman

Make Vim your friend in 9 minutes (or less)

Clearly it takes years to truly master Vim, but it takes just 9 minutes, or less depending on the speed you read at, to hear someone else’s journey with Vim. Omer Hamerman shared the “why” and “how” of Vim — plus the recipe and resources he used to learn Vim.

How did I do it? After a few brutal fights, having my fallback IDE to run back to crying with the tail between my legs, I made a decision. Here’s how I did it:

  1. Got a nice small notebook I could carry around
  2. I bought the awesome Practical Vim by Drew Neil both in hardcover and for my iPad to read on the move
  3. Every night before going to bed, I read one tip — the book is very intelligently built like that for easy, slow studying…
0:00 / 0:00