Joined May 2013
·

Samuel Lampa

Stockholm
·
·
·

@adevore3, the command just outputs to stdout, so to do logging, you will have to either pipe directly to a file. Just updated the tip with some more info about that. Thanks for the constructive feedback!

There are always tons of clever ways to do things, but for a lot of us out here, it is sometimes only the simple ones that are simple enough to stick.

As said in the beginning of the main post, figuring this out was motivated in the first place by seeing even seasoned vim:ers hacking their keyboards into pieces (to my mental frustration to death) by moving around one line/character at a time.

I last saw this in a YouTube video from a conference talk demonstrating the power of vim!

Do you start to see my point? Obviously there is some snag here, making even these vim experts neglect some of the most basic commands.

Some times something really simple is what is needed.

a-b: I have learnt them, and I use them. Still, I find this to be a complement that I use all the time.

I use the Ctrl+u/d keys a lot as well, but that doesn't have the same behavior, since it does not clearly show where the marker is in the code. It works well when just reading text/code, but when you want to quickly go to a specific point in a code for doing an insertion, moving the marker directly just works much better.

Thanks for sharing, solved my problem!

Achievements
265 Karma
14,192 Total ProTip Views