// Comment.nvim

^{⚡ Smart and Powerful commenting plugin for neovim ⚡}

✨ Features

Supports commentstring. Read more
Prefers single-line/linewise comments
Supports line (//) and block (/* */) comments
Dot (.) repeat support for gcc, gbc and friends
Count support ([count]gcc only)
Left-right (gcw gc$) and Up-Down (gc2j gc4k) motions
Use with text-objects (gci{ gbat)
Supports pre and post hooks
Custom language/filetype support
Ignore certain lines, powered by Lua regex

🚀 Installation

With packer.nvim

use {
    'numToStr/Comment.nvim',
    config = function()
        require('Comment').setup()
    end
}

With vim-plug

Plug 'numToStr/Comment.nvim'

" Somewhere after plug#end()
lua require('Comment').setup()

⚒️ Setup

First you need to call the setup() method to create the default mappings.

require('Comment').setup()

VimL

lua << EOF
require('Comment').setup()
EOF

Configuration (optional)

Following are the default config for the setup(). If you want to override, just modify the option that you want then it will be merged with the default config.

{
    ---Add a space b/w comment and the line
    ---@type boolean
    padding = true,

    ---Whether the cursor should stay at its position
    ---NOTE: This only affects NORMAL mode mappings and doesn't work with dot-repeat
    ---@type boolean
    sticky = true,

    ---Lines to be ignored while comment/uncomment.
    ---Could be a regex string or a function that returns a regex string.
    ---Example: Use '^$' to ignore empty lines
    ---@type string|function
    ignore = nil,

    ---Create basic (operator-pending) and extended mappings for NORMAL + VISUAL mode
    ---@type table
    mappings = {
        ---operator-pending mapping
        ---Includes `gcc`, `gcb`, `gc[count]{motion}` and `gb[count]{motion}`
        basic = true,
        ---extra mapping
        ---Includes `gco`, `gcO`, `gcA`
        extra = true,
        ---extended mapping
        ---Includes `g>`, `g<`, `g>[count]{motion}` and `g<[count]{motion}`
        extended = false,
    },

    ---LHS of toggle mapping in NORMAL + VISUAL mode
    ---@type table
    toggler = {
        ---line-comment keymap
        line = 'gcc',
        ---block-comment keymap
        block = 'gbc',
    },

    ---LHS of operator-pending mapping in NORMAL + VISUAL mode
    ---@type table
    opleader = {
        ---line-comment keymap
        line = 'gc',
        ---block-comment keymap
        block = 'gb',
    },

    ---Pre-hook, called before commenting the line
    ---@type function|nil
    pre_hook = nil,

    ---Post-hook, called after commenting is done
    ---@type function|nil
    post_hook = nil,
}

The configuration is also exported by the following method. But make to sure to call setup first.

require('Comment').get_config()

🔥 Usage

When you call setup() method, Comment.nvim sets up some basic mapping which can used in NORMAL and VISUAL mode to get you started with the pleasure of commenting stuff out.

Basic mappings

These mappings are enabled by default. (config: mappings.basic)

NORMAL mode

`gcc` - Toggles the current line using linewise comment
`gbc` - Toggles the current line using blockwise comment
`[count]gcc` - Toggles the number of line given as a prefix-count
`gc[count]{motion}` - (Op-pending) Toggles the region using linewise comment
`gb[count]{motion}` - (Op-pending) Toggles the region using linewise comment

NOTE: Dot repeat is not supported with [count]gcc

VISUAL mode

`gc` - Toggles the region using linewise comment
`gb` - Toggles the region using blockwise comment

Extra mappings

These mappings are enabled by default. (config: mappings.extra)

NORMAL mode

`gco` - Insert comment to the next line and enters INSERT mode
`gcO` - Insert comment to the previous line and enters INSERT mode
`gcA` - Insert comment to end of the current line and enters INSERT mode

Extended mappings

These mappings are disabled by default. (config: mappings.extended)

NORMAL mode

`g>[count]{motion}` - (Op-pending) Comments the region using linewise comment
`g>c` - Comments the current line using linewise comment
`g>b` - Comments the current line using blockwise comment
`g<[count]{motion}` - (Op-pending) Uncomments the region using linewise comment
`g<c` - Uncomments the current line using linewise comment
`g<b`- Uncomments the current line using blockwise comment

VISUAL mode

`g>` - Comments the region using single line
`g<` - Unomments the region using single line

Examples

# Linewise

`gcw` - Toggle from the current cursor position to the next word
`gc$` - Toggle from the current cursor position to the end of line
`gc}` - Toggle until the next blank line
`gc5l` - Toggle 5 lines after the current cursor
`gc8k` - Toggle 8 lines before the current cursor
`gcip` - Toggle inside of paragraph
`gca}` - Toggle around curly brackets

# Blockwise

`gb2}` - Toggle until the 2 next blank line
`gbaf` - Toggle comment around a function (w/ LSP/treesitter support)
`gbac` - Toggle comment around a class (w/ LSP/treesitter support)

Methods

Comment.nvim also provides some methods apart from the mappings. Also note that these methods only do linewise commenting and only on the current line.

-- Comments the current line
require('Comment').comment()

-- Uncomments the current lines
require('Comment').uncomment()

-- Toggles the current lines
require('Comment').toggle()

⚙️ API

Read API for more crazy stuff.

🎣 Hooks

There are two hook methods i.e pre_hook and post_hook which are called before comment and after comment respectively. Both should be provided during setup().

pre_hook - This method is called with a ctx argument before comment/uncomment is started. It can be used to return a custom commentstring which will be used for comment/uncomment the lines. You can use something like nvim-ts-context-commentstring to compute the commentstring using treesitter.

{
    ---@param ctx Ctx
    pre_hook = function(ctx)
        return require('ts_context_commentstring.internal').calculate_commentstring()
    end
}

-- or with some spicy logic
{
    ---@param ctx Ctx
    pre_hook = function(ctx)
        local u = require('Comment.utils')
        if ctx.ctype == u.ctype.line or ctx.cmotion == u.cmotion.line then
            -- Only comment when we are doing linewise comment or up-down motion
            return require('ts_context_commentstring.internal').calculate_commentstring()
        end
    end
}

Also, you can set the commentstring from here but i won't recommend it for now.

{
    ---@param ctx Ctx
    pre_hook = function(ctx)
        -- Only update commentstring for tsx filetypes
        if vim.bo.filetype == 'typescriptreact' then
            require('ts_context_commentstring.internal').update_commentstring()
        end
    end
}

post_hook - This method is called after commenting is done. It receives the same 1) ctx, the lines range 2) start_row 3) end_row 4) start_col 5) end_col.

NOTE: If methods are used, then post_hook will receives only two arguments 1) ctx and 2) -1 indicating the current line

{
    ---@param ctx Ctx
    ---@param start_row integar
    ---@param end_row integar
    ---@param start_col integar
    ---@param end_col integar
    post_hook = function(ctx, start_row, end_row, start_col, end_col)
        if start_row == -1 then
            -- do something with the current line
        else
            -- do something with lines range
        end
    end
}

The post_hook can be implemented to use newlines instead of padding e.g. for commenting out code in C with #if 0. You can find an example here.

NOTE: When pressing gc, gb and friends, cmode (Comment mode) inside pre_hook will always be toggle because when pre-hook is called, in that moment we don't know whether gc or gb will comment or uncomment the lines. But luckily, we do know this before post_hook and this will always receive either comment or uncomment status

🚫 Ignoring lines

You can use ignore to ignore certain lines during comment/uncomment. It can takes lua regex string or a function that returns a regex string and should be provided during setup().

NOTE: Ignore only works when with linewise comment. This is by design. As ignoring lines in block comments doesn't make that much sense.

With string

-- ignores empty lines
ignore = '^$'

-- ignores line that starts with `local` (excluding any leading whitespace)
ignore = '^(%s*)local'

-- ignores any lines similar to arrow function
ignore = '^const(.*)=(%s?)%((.*)%)(%s?)=>'

With function

{
    ignore = function()
        -- Only ignore empty lines for lua files
        if vim.bo.filetype == 'lua' then
            return '^$'
        end
    end,
}

🗨️ Filetypes + Languages

Most languages/filetypes have support for comments via commentstring but there might be a filetype that is not supported. There are two ways to enable commenting for unsupported filetypes:

You can set commentstring for that particular filetype like the following

vim.bo.commentstring = '//%s'

-- or
vim.api.nvim_command('set commentstring=//%s')

Run :h commentstring for more help

You can also use this plugin interface to store both line and block commentstring for the filetype. You can treat this as a more powerful version of the commentstring

local ft = require('Comment.ft')

-- 1. Using set function

-- set both line and block commentstring
ft.set('javascript', {'//%s', '/*%s*/'})

-- Just set only line comment
ft.set('yaml', '#%s')

-- 2. Metatable magic

-- One filetype at a time
ft.javascript = {'//%s', '/*%s*/'}
ft.yaml = '#%s'

-- Multiple filetypes
ft({'go', 'rust'}, {'//%s', '/*%s*/'})
ft({'toml', 'graphql'}, '#%s')

PR(s) are welcome to add more commentstring inside the plugin

🧵 Comment String

Although, Comment.nvim supports neovim's commentstring but unfortunately it has the least priority. The commentstring is taken from the following place in the respective order.

pre_hook - If a string is returned from this method then it will be used for commenting.
ft_table - If the current filetype is found in the table, then the string there will be used.
commentstring - Neovim's native commentstring for the filetype

There is one caveat with this approach. If someone sets the commentstring (w/o returning a string) from the pre_hook method and if the current filetype also exists in the ft_table then the commenting will be done using the string in ft_table instead of using commentstring

🧠 Comment Context

The following object is provided as an argument to pre_hook and post_hook functions.

I am just placing it here just for documentation purpose

---Comment context
---@class Ctx
---@field ctype CType
---@field cmode CMode
---@field cmotion CMotion

CType (Comment type), CMode (Comment mode) and CMotion (Comment motion) all of them are exported from the plugin's utils for reuse

require('Comment.utils').ctype.{line,block}

require('Comment.utils').cmode.{toggle,comment,uncomment}

require('Comment.utils').cmotion.{line,char,v,V}

🤝 Contributing

There are multiple ways to contribute reporting/fixing bugs, feature requests. You can also submit commentstring to this plugin by updating ft.lua and sending PR.

💐 Credits

tcomment - To be with me forever and motivated me to write this.
nvim-comment - Little and less powerful cousin. Also I took some code from it.
kommentary - Nicely done plugin but lacks some features. But it helped me to design this plugin.

🚗 Roadmap

Live upto the expectation of tcomment
Basic INSERT mode mappings
Doc comment i.e /**%s*/ (js), ///%s (rust)
Inbuilt context commentstring using treesitter

{
    pre_hook = function()
        return require('Comment.ts').commentstring()
    end
}

Header comment

----------------------
-- This is a header --
----------------------

tjdevries / Comment.nvim