3 ms·
Ironically text editing is the thing I like least about vim. I would switch to an IDE if it provided the level of programmability Vim has. For example, I have a
by PhilipRoman 2y ago
Ironically text editing is the thing I like least about vim. I would switch to an IDE if it provided the level of programmability Vim has. For example, I have a binding which, when used on a netlink command, opens the corresponding implementation in the kernel. How do you do that in something like VSCode? I guess I could write an extension, but in Vim it takes like 2 lines of code that you write once and forget about it.
Or another example - you can analyze log files in terminal buffer by folding based on patterns, multi-color highlighting, etc.
- phatskat 2y agoThe ability to quickly and easily(-ish) script vim is incredibly useful. At one point, because of environment constraints, the easiest way to run unit tests was either to run them all or to specify the file I wanted to test. A little bit of googling and playing around and I had Vim read my current spec name, chop it up to find the correct source file name, spawn a terminal and run the test command using that source name anytime I wrote a change. Thankfully I’m somewhere with sane tooling that watches for changes and only runs relevant tests, but back then this little foray into “how do I make Vim do a thing” saved me a ton of time.