Build Status

| Service | Status | | ------------- |:-------------:| -----:| | Travis CI | | | AppVeyor | |

Introduction

The below are the examples in "filetype=c". caw.vim supports 300+ filetypes (see |caw-supported-filetypes|).

Type "gci" (toggle: "gcc", uncomment: "gcui")
  before:
      "   <- inserted here"
  after:
      "   # <- inserted here"

Type "gcI" (uncomment: "gcuI")
  before:
      "   inserted the first column"
  after:
      "#    inserted the first column"

Type "gca" (uncomment: "gcua")
  before:
      "inserted after this"
  after:
      "inserted after this    # "

Type "gcw" (uncomment: "gcuw")
  before:
      "  wrap!"
  after:
      "  /* wrap! */"

Type "gcb"
  before:
      "  box!"
  after:
      "  /********/"
      "  /* box! */"
      "  /********/"

Type "gco"
  before:
      "   func1();"
  after:
      "   func1()"
      "   // "  (now cursor is at the end and entered insert-mode)

Type "gcO"
  before:
      "   func1();"
  after:
      "   // "  (now cursor is at the end and entered insert-mode)
      "   func1();"

Features

• Supports 300+ filetypes (see |caw-supported-filetypes|).
  • But caw.vim does not slow down your Vim startup because each comment string are defined at ftplugin files (after/ftplugin//caw.vim).
• Supports operator mappings (|caw-keymappings-operator|).
  • If |g:caw_operator_keymappings| is non-zero, all default keymappings map to operator mappings.
• Supports also non-operator mappings (|caw-keymappings-non-operator|).
• Dot-repeatable if you installed repeat.vim
• The comment behavior only depends on 'filetype' by default. But if you have installed context_filetype.vim, caw.vim also depends on the filetype of the context of the current cursor location. So you can comment/uncomment JavaScript in HTML correctly.
• Well-tested powered by themis.vim