|
|
|
|
|
|
by diegs
2174 days ago
|
|
|
i tried to switch to emacs+evil, but i can't bring myself to do it. partly because I'd have to invest a lot of time in getting an equivalently productive environment, but partly because of the following 1. vi is everywhere, and... 2. vi with no plugins is still super powerful, which is helpful on random hosts / coworker's machines / basically anywhere, and... 3. since vi is still so powerful out of the box, i only need a few lightweight plugins to close the loop and make the most powerful editor i can imagine needing. 99% of my plugin usage is fzf and ale w/lsp, which are arguably two very powerful plugins, but the cognitive overhead is very low, and at least among peers my editor doesn't seem to be slowing me down at all i would also pose the controversial opinion/hot take that using a less "powerful" (non-IDE) editor helps you write better code. humans can only fit so much into their working memory at a time. vim doesn't really let me do crazy refactors or jump through endless chains of class hierarchies (well, with lsp it can, but...). compared to my eclipse/intellij days (and codebases worked on by other people using those tools) i am forced to tame complexity by defining good module boundaries and abstraction barriers. |
|
|
Even that can be handled by Vim ootb, just add
to your vimrc and you're set, you can recursively :find pretty much anything in the folder where you opened Vim and you can even go fuzzy, for how it works in practice: https://youtu.be/XA2WjJbmmoM?t=493