dot_vim
My 12 Year-Old (Neo)Vim Configuration (by mutewinter)
kommentary
Neovim commenting plugin, written in lua. (by b3nj5m1n)
| dot_vim | kommentary | |
|---|---|---|
| 1 | 14 | |
| 679 | 533 | |
| - | - | |
| 7.0 | 2.9 | |
| about 2 months ago | 5 months ago | |
| Vim Script | Lua | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dot_vim
Posts with mentions or reviews of dot_vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-14.
-
A pragmatic approach to migrating from VSCode to Neovim
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”.
kommentary
Posts with mentions or reviews of kommentary.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-14.
-
A pragmatic approach to migrating from VSCode to Neovim
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.
-
Question: Is it a requirement that plugins written in Lua require you to call the setup function?
Here’s an example of a lua plugin with no setup function
-
TakeTuesday: Comment.nvim tutorial
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.)
-
Comment.nvim: new stuff that will make you Rick Roll.
A bit unrelated, but I wrote some tests for kommentary that might inspire you to create a test suite for this plugin too.
-
Comment.nvim: Simple and powerful comment plugin for neovim. Supports commentstring, dot repeat, left-right/up-down motions, hooks, and more
Dot repeat https://github.com/b3nj5m1n/kommentary/issues/41
-
Comment C/C++ line or block
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
-
nerdcommenter seems to better figure out what comment syntax to use than vim-commentary, but i like vim-commentary more at everything else
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 .
-
Aspiring plugin authors: look at kommentary
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.
-
commented.nvim, a commenting plugin that actually works with count.
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.
-
Custom keymap function does not work with `<Plug>` commands
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.
What are some alternatives?
When comparing dot_vim and kommentary you can also consider the following projects:
termux_confs - personalization configs for termux setup
nvim-comment - A comment toggler for Neovim, written in Lua
nvim-lua-guide - A guide to using Lua in Neovim
vim-commentary - commentary.vim: comment stuff out
language-server-protocol - Defines a common protocol for language servers.
Comment.nvim - :brain: :muscle: // Smart and powerful comment plugin for neovim. Supports treesitter, dot repeat, left-right/up-down motions, hooks, and more
tree-sitter - An incremental parsing system for programming tools
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
nvim-tree.lua - A file explorer tree for neovim written in lua
commented.nvim - Neovim commenting plugin in Lua. Support operator, motions and more than 60 languages! :fire:
dotfiles - My Linux dotfiles
tcomment_vim - An extensible & universal comment vim-plugin that also handles embedded filetypes
dot_vim vs termux_confs
kommentary vs nvim-comment
dot_vim vs nvim-lua-guide
kommentary vs vim-commentary
dot_vim vs language-server-protocol
kommentary vs Comment.nvim
dot_vim vs tree-sitter
kommentary vs nvim-ts-context-commentstring
dot_vim vs nvim-tree.lua
kommentary vs commented.nvim
dot_vim vs dotfiles
kommentary vs tcomment_vim