|
|
|
|
|
by gsinclair
1622 days ago
|
|
The editing task you set is admirably met with VSCodium, indeed, but the task itself seems irrelevant to real coding. In what circumstance do you see that three disparate changes of that nature all need to be made? In reality, you would think about and act upon each in turn. In Vim, I would use db and . and . after navigating to the necessary places, perhaps using search. At all times, I would a perfectly content vim user. (But yes, I’m sure there are plenty of situations where mouse and multi-cursor make a great approach.) I look forward to seeing international text editing competitions appear on YouTube! |
|
Here's a real example from real coding I was doing, then:
I want to bump the 'r' and 'b' from 42 up to 255 but leave 'g' alone. So I, With a vim I could Alternatively with vim It's funny all these posts presuming that multi-cursor is a gimmick only used by idiots who don't know how to use regular expression query replace and the vim '.' command. Yeah, I know how to use those, and multi-cursor is often faster. And VSCodium has a powerful multi-file query-replace that is faster to learn than the equivalent vim/emacs/grep/sed.