Spent a good amount of time trying to fix a really weird bug in Neovim yesterday. After a while I gave up and tried to get Fable to help me.

Definitely one of those things that seems really obvious afterwards, and I can't believe it didn't bite me earlier. Here's the story...

I’m pretty excited about this one. I’ve been using EasyMotion for a long time - before Neovim existed, and after, even though it seemed to go out of style (see https://github.com/neovim/neovim for more information about why). There are lots of alternatives, like leap.nvim, flash.nvim, sneak.nvim and etc, but they all required typing more characters, or didn’t work across windows, or were just generally buggy. I stuck with EasyMotion; it just worked for me, even despite it’s drawbacks. Until it didn’t. Recently, it has started crashing Neovim. I reported the issue, but no response. EasyMotion is quite old and it doesn’t appear as though anyone is working on it anymore.

I found a solution, though, and that is to write a custom hop.nvim command that works like EasyMotion used to. Read the rest of the article if you want to see how to do it!

Yesterday, after many years of using Vim, I’ve finally realized what the purpose of Vim Tabs is. My friend asked me to post this article, because she was also stumped by their functionality.

Here’s a little info about how/why I got into vim …