-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this still needed with Neovim 0.10? #453
Comments
A notable difference is that the built-in comment does not force the single-space inner padding. This means that comments would be |
Additionally, NeoVim cannot distinguish between block and line comments. In C, e.g., it will always insert block comments. |
As I know the built-in commenting support in Neovim 0.10 actually comes from mini.comment that lacks block commenting support and some other features. |
The limitation voiced by @ouuan does apply to C and Java, but not to Lua or Python. I think that, for now, this plugin provides a more consistent and featureful commenting interface, and agree that a comparison should be provided in the README. |
UPDATE: I can't say anything about @flexagoon If you don't need block comments, then you are good with the default Neovim behavior, at least try it and decide for yourself.
I don't see that, standard
|
What's your |
@ouuan interesting for *.ts files it's I came back to this, to update my original comment: default comment doesn't work for sql, like at all. |
Can NeoVim With this plugin I press |
@VladimirMarkelov no, it can't. It can only comment whole line. |
Neovim 0.10 introduced built-in commenting support:
neovim/neovim#28176
Does it make this plugin redundant? If not, the differences should be mentioned in the readme.
The text was updated successfully, but these errors were encountered: