This one gives a score of 32, but I like it just for the sheer one-liner obsfucatedness: :g/#/+1s/\v(.*)\n.*/\1\r\1
ed golf, eh?
VimGolf.com - real Vim ninjas count every keystroke
71–80 of 86 posts
Re: VimGolf.com - real Vim ninjas count every keystroke
#72Re: VimGolf.com - real Vim ninjas count every keystroke
#73Re: VimGolf.com - real Vim ninjas count every keystroke
#74Re: VimGolf.com - real Vim ninjas count every keystroke
#75Earlier quoted context omitted.
I'm logging the solutions, but in real MVP fashion... not showing them just yet. Need to bootstrap a vimscript parser first. If anyone is up for it, would love some help with the client/parser: https://github.com/igrigorik/vimgolf
MVP meaning 'Most Valuable Player'?
"Maximum reVivification Potential" gets my vote.
Re: VimGolf.com - real Vim ninjas count every keystroke
#76I had an idea for an emacs version of this. Anyone have any ideas on how you'd implement this with emacs?
You could check keystrokes used with C-h l (or M-x view-lossage), but Emacs's whole design is based on extensibility rather than terse, orthogonal, and (usually) single-key commands. Don't find a clever way to knock it down to 30 keystrokes (or whatever) - when you notice a common operation, script it, name it, bind it, now it's two or three keystrokes.
Re: VimGolf.com - real Vim ninjas count every keystroke
#77Where are the solutions? That's the fun thing about Perl golf is seeing how people did it in X characters. Without solutions...well, I don't see the point.
I'm logging the solutions, but in real MVP fashion... not showing them just yet. Need to bootstrap a vimscript parser first. If anyone is up for it, would love some help with the client/parser: https://github.com/igrigorik/vimgolf
Good news. You can now preview the solutions!
Only one wrinkle: you have to submit your own challenge to see the solutions.
Re: VimGolf.com - real Vim ninjas count every keystroke
#78Re: VimGolf.com - real Vim ninjas count every keystroke
#79Earlier quoted context omitted.
I'm logging the solutions, but in real MVP fashion... not showing them just yet. Need to bootstrap a vimscript parser first. If anyone is up for it, would love some help with the client/parser: https://github.com/igrigorik/vimgolf
I will take part in this when the solutions are displayed. All the fun is in the solutions. So for me, hiding them kills the whole point of the project. Otherwise it would be lots of fun. Im a long time vim user and love it.
I think Project Euler has a good compromise - you can see (and comment on!) solutions once you've successfully passed some baseline. Then you don't feel like you cheated, but can pick apart their solutions, now that you've already focused on that problem for a while.
I've learned a LOT figuring out how some outstanding PE submissions worked, translating their algorithms to my favorite languages.
Re: VimGolf.com - real Vim ninjas count every keystroke
#80FizzBuzz: (score: 71) i1^] qaYp CTRL+a q98@aggjjqaA Fizz^] 3jq32@agg:5 ENTER qaA Buzz^] 5jq19@a:%s/z B/zB/ ENTER ZZ
[deleted]