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

Box it - 6340 entries

Create a box around a line.

  • Best score: 21
  • Best player score: 21
  • Number of attempts: 8
JSON string rotation - 51 entries

Right value strings are misplaced. Just rotate them! I'm too kind with you guys and didn't included "strings with \" in it"!

  • Best score: 19
  • Best player score: 19
  • Number of attempts: 11
Add semicolons - 8222 entries

Simply add a semicolon at the end of each line

  • Best score: 10
  • Best player score: 10
  • Number of attempts: 5
prepend * to every non-blank line - 3357 entries

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

  • Best score: 10
  • Best player score: 10
  • Number of attempts: 4
Collect List - 3930 entries

Convert to comma separated list.

  • Best score: 12
  • Best player score: 12
  • Number of attempts: 5
Split line with dots - 2021 entries

This line is too long, split it.

  • Best score: 15
  • Best player score: 15
  • Number of attempts: 7
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: 17
  • Number of attempts: 2
One number per line - 16645 entries

Just give me the numbers.

  • Best score: 14
  • Best player score: 14
  • Number of attempts: 8

Contributed Challenges

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.

Sylvain Leroux / Yes, I Know IT !
Twitter:

Sylvain Leroux. Engineer by Passion, Teacher by Vocation. My goals : to share my enthusiasm for what I teach

entered into 8 challenges

contributed 1 challenges