Becoming a fzf master A Practical Guide to fzf: Building a File Explorer A Practical Guide to fzf: Shell Integration A Practical Guide to fzf: Vim Integration A Practical Guide to fzf: Building a Git Explorer It’s again a boring day in the offices of MegaCorpMoneyMaker, the company you’re working with. As often you’re writing spaghetti code, not because you’re a bad developer, but because your deadlines are incredibly short, your motivation non-existent, and your colleagues care more about their promotions than their actual work.

The sun is shining today; too bad, you’re stuck in the office of your beloved company, MegaCorpMoneyMaker. Your task is to delete specific lines across thousands of XML files; it’s the “API” of an external warehouse, and, as always, they screwed it up. You begin to write a script using your favorite programming language, when suddenly Davina, your colleague developer, comes to your desk: “You know that you don’t have to write a script to do that?

This article is the third part of a series about fzf: Becoming a fzf master A Practical Guide to fzf: Building a File Explorer A Practical Guide to fzf: Shell Integration A Practical Guide to fzf: Vim Integration A Practical Guide to fzf: Building a Git Explorer Davina, your colleague developer, explained in the two previous articles of the series how to use and configure fzf for the shell. This time, she’s back to explain how to use fzf directly in the Best Editor in the Known Universe™, Emacs Vim (or Neovim).

It’s rainy and dark outside, and it’s not going better inside: another depressing day at MegaCorpMoneyMaker, the company you’re working for. Of course, you need to debug the 28925th bug of the day; some cursed prices made their way into the database, finally reflecting the real value of the low quality products the company is selling. Your manager, of course, doesn’t see this unfortunate change as positively. These prices are imported from files you’re fetching from an FTP.

Another boring day at MegaCorpMoneyMaker, the company you’re working with. You have the most exciting task anybody would ask for: modifying the README of an obscure microservice due to recent changes from your team. Looking at the project, you realize that it has way too many files, and worse, that the readme file is nowhere to be found! Anxious, you ask Davina, your colleague developer, how to find this file. She tries to help: