kommentary VS dot_vim

Indent-blankline to draw indentation guides, nvim-autopairs to automatically complete pairs of brackets and quotes (I didn’t know I couldn’t live without it), nvim-ts-autotag to autocomplete pairs of tags as well, targets.vim to target what is inside or outside the mentioned pairs and vim-surround to manage all those pairs with few keystrokes. Kommentary to comment and uncomment lines of code, nvim-cursorline to help locate where the cursor is and nvim-colorizer because I am cheeky. Vim-abolish is definitely an interesting one. I decided to install it because of its case coercion capabilities, but it can do much more than that.

Here’s an example of a lua plugin with no setup function

The one I use is kommentary.nvim. A) It works, and with embedded code too, but also b) the Lua underneath it is really good. It’s well-commented, tested, and just generally a good resource to learn Lua from (or at least it has been for me.)

A bit unrelated, but I wrote some tests for kommentary that might inspire you to create a test suite for this plugin too.

Dot repeat https://github.com/b3nj5m1n/kommentary/issues/41

I'm still using the tpopes plugin, so I don't really know about the Lua versions 😅. But I have heard good things about kommentary

I've been using b3nj5m1n/kommentary . I's uses are similar to vim-comentary . It has option to use only single line comments . This can be used to avoid /* ... */ . You can try that out .

b3nj5m1n/kommentary is one that is relatively small, but big enough to be interesting. It is also *insanely* well documented and the overall code quality seems good to me.

I need a comment plugin that works in normal mode and virtual mode and accepts count. Neither does kommentary and nvim-comment provide counts, therefore I decided to write one for myself.

I can import this function and use it with all my custom keybindings. However, it doesn't custom keybindings I want to use for the Kommentary plugin.

Whilst going through more tutorials and articles, it was becoming clear customising Vim to one’s needs is among the strongest selling points of the editor, and can become a never ending task. I needed to formalise a definition of done which could give me boundaries. Therefore, I compiled a list of functionalities I believed to be indispensable, based on what in VSCode I valued the most. I would follow the list and flibber-jibber the frammistan to achieve similar results following “the vim way”.