News for hackers. Stuff that matters.
Re:Vim Anywhere by lucb1e on Saturday February 17, 2018 @07:23AM (#16400377)
And hjkl is not the arrow keys' replacement, as many non-users think.

There are a hundred other ways to move around a file, each of which are more efficient than hitting a button ten times. Those kinds of things are what makes Vim convenient (though not having to move your hand to the arrow keys for going one line down is pretty convenient, too).

Re:Vim Anywhere by MaxBarraclough on Saturday February 17, 2018 @04:06PM (#16402697)
I'm a Vim fan, but that's a little disingenuous.

Ordinary text editors have ctrl-left and ctrl-right, which are equivalent to Vim's w and b. They also have Home/End and ctrl-f.

Re:Vim Anywhere by ibotty on Sunday February 18, 2018 @05:38AM (#16405393)
But w and b are not the end of vi's (let alone vim's/neovim's + plugins') motions.
Re:Vim Anywhere by MaxBarraclough on Sunday February 18, 2018 @06:16AM (#16405517)
Sure, but it's not often I win big by using Vim's advanced movement commands.
Re:Vim Anywhere by zweicoder on Monday February 19, 2018 @04:01AM (#16411653)
One of the most useful Vim motions for me has been repeating j / k for n times, e.g using 12j to jump down 12 lines.

Combined with relative line numbers (to show how many lines to jump up / down) this has been a really big win for me to navigate around text.

Re:Vim Anywhere by jsjohnst on Sunday February 18, 2018 @12:41PM (#16407140)
Shift-G / gg are “big” wins for me on a fairly regular basis.
Re:Vim Anywhere by MaxBarraclough on Sunday February 18, 2018 @01:20PM (#16407323)
That's a good example, but I suspect most editors/IDEs have their own equivalent shortcuts.

Apparently in Visual Studio it's SHIFT+CTRL+HOME.

Re:Vim Anywhere by jsjohnst on Sunday February 18, 2018 @01:48PM (#16407471)
Not all keyboards have a home key and the vast majority have a shift/g key, but yes, i agree.
Re:Vim Anywhere by ibotty on Monday February 19, 2018 @05:30AM (#16412008)
you don't use `)` or any other object motion? You should (consider)! `:help object-motions`