kommentary VS nvim-ts-context-commentstring

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

If you already know b3nj5m1n/kommentary, could you say what are the advantages/inconvenients of each one ?

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 .

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 just installed kommentary a few hours ago.

I work with Vue every day, but I don't use AstroNvim. The Volar language server with Take Over Mode works great for me. I don't know what exactly is broken for you when commenting, but my plugin nvim-ts-context-commentstring works for setting the correct commentstring in the Vue single file component sections with Treesitter.

Fair enough, although this helps a lot with this issue.

I haven't tried mini, but judging by the README he would also have to use a plugin the likes of nvim-ts-commentstrung in a p re / post hook to get the adequate comment string in files with multiple languages.

I use https://github.com/JoosepAlviste/nvim-ts-context-commentstring with vim-commentary

I think you could use Comment.nvim combine with nvim-ts-context-commentstring like explained in this video

you should be able to integrate it with nvim-ts-context-commentstring as specified in the nvim-comment README

You can try using comment + context-comment, I've found it better for treesitter supported code commenting personally.

I'm using Context Commentstring & Comment.nvim together.

I think you're asking why Neovim chose to use tree-sitter for syntax highlighting over LSP? In addition to its speed over LSP and no dependency on a separate running server, tree-sitter is described as an incremental parsing library. When editing source code, until the user stops writing the syntax is usually considered incorrect and the code is in a broken state. Tree-sitter was designed to handle these sorts of syntax errors and highlight the rest of the file correctly while the current section is being edited. Tree-sitter also boasts a few unique features over LSP. Language injection is a cool feature where tree-sitter can parse multiple languages in the same source file and provide the correct highlighting for both languages. Common examples include HTML inside JSX, vimscript inside Neovim's Lua API, C code in Lua, Bash code inside Dockerfiles, etc. Furthermore the language injection feature can be extended like in the very cool nvim-ts-context-commentstring plugin that detects the current language under the cursor and applies the corresponding commentstring. Additionally tree-sitter allows the user to extend the concept of textobjects using the tree-sitter query language. The plugin nvim-treesitter-textobjects provides a collection of queries for common languages that define text objects such as classes, functions, parameters, etc. In turn this allows you to perform operations such as delete the contents of a function (using the motion dif), delete an entire class and enter insert mode (using the motion cac), and navigate to the next function (using the motion ]m).