News for hackers. Stuff that matters.
Re:A Good Vimrc by dougblack on Saturday October 10, 2015 @10:23AM (#10365586)
Hi! Author here.

Fair points. I'm gonna start out on the defensive: I didn't post the article, which kinda stinks because if I knew it was going to get such attention I would have updated it to my current setup. Anyways as the 1.5 year old article states:

  This article will almost certainly fall out of date with my vimrc in the very near future
I don't do jk escape anymore. I have since abandoned custom escapes because I work often enough on remote servers with vanilla vimrcs that don't have custom escape bindings set that the penalty I pay having to stop and consider which environment I'm in before every escape wasn't worth the small quality of life enhancement from having it set locally.

Good tip on caps lock, though I currently have it set to control which I find is a much better use of the key. Especially once you know about ctrl-o.

Re:A Good Vimrc by chris_wot on Saturday October 10, 2015 @11:12AM (#10365722)
I once told my wife an amusing story I'd read in Australian Personal Computer where a computer technician was told by a secretary that she was great with computers, said technician was very happy and joked that he was glad as the last person he had to help thought that the way to input capital letters was to press the caps lock key, the capital letter and then press the caps lock key again... To which the secretary asked "what's so funny about that?"

Anyway, I chortled after telling this to my wife, to which she looked at me with a puzzled look and asked me what the punchline was...

Re:A Good Vimrc by falcolas on Saturday October 10, 2015 @03:22PM (#10366636)
To be fair, some of the fastest typists use caps lock instead of shift, since it makes the shift action modal, instead of requiring coordination of multiple fingers at once.

http://forum.colemak.com/viewtopic.php?id=1309

Re:A Good Vimrc by chris_wot on Saturday October 10, 2015 @08:50PM (#10367578)
Oh! My wife will be pleased :-)
Re:A Good Vimrc by lmohseni on Saturday October 10, 2015 @12:18PM (#10365955)
You may wish to look into xcape. Currently i have capslock = escape when pressed alone, or control when pressed with another key. [0] https://github.com/alols/xcape
Re:A Good Vimrc by mateuszf on Saturday October 10, 2015 @02:15PM (#10366368)
> Currently i have capslock = escape when pressed alone, or control when pressed with another key.

This is brilliant idea. And it works on OSX too - using http://apple.stackexchange.com/a/132569

Re:A Good Vimrc by hyyypr on Saturday October 10, 2015 @01:30PM (#10366192)
Thank you for this! I've been using capslock as Ctrl for a long time time, and fell into the bad habit to use C-c to exit insert mode.
Re:A Good Vimrc by Dobbs on Saturday October 10, 2015 @11:26AM (#10365785)
ctrl+] will act as escape in any vim out there. At least that I've encountered.

Having caps as ctrl makes it really easy to hit.

Re:A Good Vimrc by geofft on Saturday October 10, 2015 @02:11PM (#10366353)
Ctrl-C seems to work in any vim (though, I think, not actual vi), and at some point my muscle memory rewired itself to that. It's usually directly under my left hand, and it's a keyboard shortcut I use elsewhere, like in the shell.
Re:A Good Vimrc by 0942v8653 on Saturday October 10, 2015 @01:35PM (#10366210)
ctrl+[ works in any vim because it sends the exact same character as Escape. Unless your terminal emulator is very oddly configured, then it will work the same.
Re:A Good Vimrc by krick on Saturday October 10, 2015 @12:51PM (#10366073)
ctr+[ you mean.
Re:A Good Vimrc by tvararu on Tuesday October 13, 2015 @04:39AM (#10379186)
This depends on what you're hosting your article on, but you could either generate the vimrc programatically from the code in the article or generate the article from comments placed in your vimrc. Similar to a .litcoffee file.
Re:A Good Vimrc by atatus on Saturday October 10, 2015 @12:52PM (#10366076)
Do you think that updating your article would make more sense now. It would benefit users who read it now.