Question 1

How do I set up custom keybindings for codetags in commented.nvim?

Accepted Answer

Define codetags_keybindings in the setup opts or use vim.api.nvim_set_keymap. For example, map fixme_line to <leader>ff in the configuration, as shown in the README's packer.nvim example.

Question 2

commented.nvim vs kommentary: which is better for Neovim?

Accepted Answer

commented.nvim is superior if you need count support and accurate uncommenting for multiple patterns, while kommentary might be simpler for basic commenting. commented.nvim also integrates better with tree-sitter plugins via hooks.

Question 3

Can I use commented.nvim with Visual Studio Code or other editors?

Accepted Answer

No, commented.nvim is designed exclusively for Neovim and relies on its Lua API. It won't work with VSCode, Vim, or other editors without significant modifications or porting efforts.

Question 4

How to add support for a new programming language in commented.nvim?

Accepted Answer

Contribute by adding comment symbols to the language definitions in the init.lua file. The README provides a link to the section where you can submit changes via pull request for community review.

Question 5

What's the performance impact of using hooks in commented.nvim?

Accepted Answer

Hooks are faster than autocommands as they don't depend on updatetime, but they add minimal overhead during commenting operations. The plugin is optimized for speed, but complex integrations might slightly affect responsiveness.

Question 6

Does commented.nvim handle nested comments in languages like CSS or JavaScript?

Accepted Answer

It handles block comments accurately, but for nested comments, it relies on commentstring definitions. Integration with tree-sitter plugins can improve handling of complex cases, but default support may vary.

commented.nvim

What is commented.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions