Real Vim ninjas count every keystroke - do you?

Pick a challenge, fire up Vim, and show us what you got.

Changelog, Rules & FAQ, updates: @vimgolf, RSS.

Your VimGolf key: please sign in

$ gem install vimgolf
$ vimgolf setup
$ vimgolf put [challenge ID]

Played Challenges

Add semicolons - 8251 entries

Simply add a semicolon at the end of each line

  • Best score: 10
  • Best player score: 12
  • Number of attempts: 2
Simple, Practical, and Common - 30386 entries

Simple things we do all the time should be able to be done with very few keystrokes, but sometimes I find something I need to do makes me go, "There MUST be a better way." This challenge is just a simple movement and entering text at a certain place.

  • Best score: 22
  • Best player score: 23
  • Number of attempts: 6
Box it - 6369 entries

Create a box around a line.

  • Best score: 21
  • Best player score: 27
  • Number of attempts: 4
prepend * to every non-blank line - 3407 entries

Prepend an asterisk to every non-blank line in the input file.

  • Best score: 10
  • Best player score: 10
  • Number of attempts: 4
I forgot quotes - 14504 entries

Oops.

  • Best score: 10
  • Best player score: 15
  • Number of attempts: 1
One number per line - 16673 entries

Just give me the numbers.

  • Best score: 14
  • Best player score: 21
  • Number of attempts: 4
Reconstruct the actual output from my unit test tool report - 95 entries

When a test fails, my unit test tool reports differences between the actual output and the expected output as follow: - line in the expected output but missing in the actual output are prefixed with a dash - unexpected lines in the actual output are prefixed with a plus sign - comments added by the unit test tool are prefixed with a question mark - common lines are showed `as-is` (well, almost;) From that "diff" format, I would like to reconstruct the actual output.

  • Best score: 16
  • Best player score: 23
  • Number of attempts: 1
Pan
Twitter:

He/him

entered into 7 challenges

contributed 0 challenges