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

Easier Align - 95 entries

Align the columns of a markdown table

  • Best score: 62
  • Best player score: 161
  • Position: #15 / 36
  • Number of attempts: 1
simple replacements - 1264 entries

The goal is to see the replacement commands in action.

  • Best score: 19
  • Best player score: 21
  • Position: #116 / 283
  • Number of attempts: 7
CSV to MD format - 330 entries

To convert a CSV list to Markdown list

  • Best score: 36
  • Best player score: 108
  • Position: #65 / 77
  • Number of attempts: 1
prepend * to every non-blank line - 6120 entries

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

  • Best score: 10
  • Best player score: 16
  • Position: #1005 / 1493
  • Number of attempts: 2
Unsemantic linewrapping - 861 entries

[Inspired by a blog post I read: https://scott.mn/2014/02/21/semantic_linewrapping/. Text adapted.] Sometimes when editing a Markdown file, I wrap the lines semantically. Instead of inserting a newline at 70 columns (or whatever), or making paragraphs one long line, I put in newlines at a point that seems logical to me. This may seem silly, but it produces better diffs. Semantic linewrapping also makes editing snappier. I can delete, edit or insert sentences easily using linewise operations. Code-oriented text editors like Vim and [REDACTED] are really good at this kind of manipulation. Editing text that hasn't been wrapped semantically is a pain, though:

  • Best score: 9
  • Best player score: 22
  • Position: #214 / 218
  • Number of attempts: 1
shaik azhar madar
Twitter:

5c3af818

entered into 5 challenges

contributed 0 challenges