News for hackers. Stuff that matters.
Re:Seven habits of effective text editing (2000) by jonahx on Monday October 23, 2017 @10:09AM (#15533252)
I'd make a few counterpoints there:

1. Even in those situations, I believe a veteran vim user would still beat someone using a mouse.

2. That said, the situation you describe is relatively rare: when coding you typically will be addressing blocks of text defined as functions; sharing an indent level ("ii" selects these); or otherwise selectable by vim in 2-3 keystrokes.

3. Even when that's not the case and the vim selection takes, say, 5 or 6 keystrokes, it has the advantage that your fingers never left the home row, so there is no wasted time "resetting."

4. Just as a tip: doing a "/" search for 2-3 characters after making your visual selection is typically enough to define your block, and will often be faster (and less of a cognitive distraction) than trying to eyeball or count the number of lines and doing a "10j" motion or similar.

Re:Seven habits of effective text editing (2000) by stabbles on Monday October 23, 2017 @10:35AM (#15533440)
> sharing an indent level ("ii" selects these)

That doesn't seem to work. Am I missing something?

Re:Seven habits of effective text editing (2000) by jonahx on Monday October 23, 2017 @10:53AM (#15533588)
I'd forgotten that I get this feature from a plugin:

https://github.com/michaeljsmith/vim-indent-object

Re:Seven habits of effective text editing (2000) by xyzzy_plugh on Monday October 23, 2017 @10:01PM (#15538662)
I've been eyeballing the number of lines (or characters) long enough that I am correct more often than not.

Also, relative line numbering changed my life.