Comment.nvim
kok.nvim
Our great sponsors
Comment.nvim | kok.nvim | |
---|---|---|
62 | 60 | |
3,520 | 3,361 | |
- | - | |
5.6 | 9.3 | |
16 days ago | 9 days ago | |
Lua | Python | |
MIT License | GNU General Public License v3.0 only |
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.
Comment.nvim
-
My 2024 PDE: NeoVim
Treesitter is a syntax parser that'll build a tree-like structure to enable anything from excellent syntax highlighting through to complex refactoring. There are so many creative ways you can use Treesitter, from jumping around text objects to commenting sections of code, it's a must-have in my books.
- Do I need a plugin manager ?
-
Noobie Needs a Nudge
A couple nice quality of life plugins would be: Comment (which lets you use a keybinding to comment/uncomment things), Autopairs (which will make the paired brackets/parentheses/etc.), and Rainbow2 (which color-matches the pairs if things like parentheses).
- [Neovim] Appel pour les tests - Intégration native JSX dans comment.nvim
-
How do I use this documentation to override default configuration? Learning the NeoVim ecosystem
I am reading the documentation for the [Comments](https://github.com/numToStr/Comment.nvim] plugin with :h comment.config and I see this
-
Plugin for comments
I was wondering what plugins you use for comments, actually, I'm using numToStr/Comment.
-
Question for lua Plugin devs.
Nowadays, people (mostly) autogenerate their help docs with either markdown or emmmylua are their source. You are facing an issue that I faced before with Comment.nvim.
-
What is the best commenter for tsx, jsx and css files with lua config
Comment.nvim?
-
Treesitter is unusable on typescript files
Based on your reply I recommend taking out the comment plugin, replacing it with https://github.com/nvim-treesitter/nvim-treesitter-textobjects and https://github.com/numToStr/Comment.nvim
- How to surround a paragraph with multiple charaters/symbols?
kok.nvim
-
How to get this overlay effect in neovim?
In the examples listed on this page https://github.com/ms-jpq/coq_nvim, there is a pattern overlay over the whole screen. Is there a neovim plugin that does this? Thanks.
-
Can anyone explain how to use treesitter with neovim in simple language?
nvim-cmp or coq_nvim is for autocompletion. Treesitter is for parsing language syntax. (I guess the most typical use case for this would be syntax highlighting.) Note that (neo)vim also has built in manual completion that you can use by setting up your omnifunc and triggering it with in insert mode .
-
What's the one plugin you'd love to see?
Aw man that's not nice to hear. I have had my own struggle with lsp not gonna lie. I used to use coc until it got too slow, after struggling for like 2 days lol lsp is working fast and neat. I'd suggest you to take a look at coq https://github.com/ms-jpq/coq_nvim which claims to be fast as fuck (literally lol) and also claims to be faster than lsp (because its written using c or something). Haven't tried it personally
-
New to Rust. How to setup Nvim as IDE?
Coq_nvim
-
Coq + LSP crashing
I'm attempting to use (coq_nvim)[https://github.com/ms-jpq/coq_nvim]. This is my config:
-
Neovim crashes when LuaSnip is used
Does your coq_nvim and nvim-lspconfig really load? Because they have opts = true
-
Is it a bad config or cmp isn't as smart as VSCode autocompletion?
I'd be happy for someone who knows more about this to correct me. But in my experience as well, nvim-cmp is not as good completion as vscode, its suggestions can be all over the place sometimes. I found that coq_nvim tends to better in this regard. I still prefer nvim-cmp for other reasons but you should definitely try coq_nvim out and see if you have a better experience.
-
nvimYAY! but: how to get coq (or any) completion to work (pyright)?
Coq_nvim isn't the same as Coc.nvim. Coq is a completion plugin with lots of caching written in Python that works alongside the builtin LSP. Coc is an LSP client (and has it's own plugin ecosystem) written in Node.
-
Why aren't there more plugins written in python?
There are some like https://github.com/SirVer/ultisnips and https://github.com/ms-jpq/coq_nvim. Speed is not really an issue, I guess people just prefer to have fewer dependencies and use lua which is already bundled in neovim.
-
nvim + lspconfig + nvim-cmp general slowness in large codebases
Maybe using coq.nvim instead of nvim-cmp could help (?) dince it caches the LSP responses. I haven't test it, though
What are some alternatives?
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
kommentary - Neovim commenting plugin, written in lua.
coq - Coq is a formal proof management system. It provides a formal language to write mathematical definitions, executable algorithms and theorems together with an environment for semi-interactive development of machine-checked proofs.
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
nvim-cmp - A completion plugin for neovim coded in Lua.
commented.nvim - Neovim commenting plugin in Lua. Support operator, motions and more than 60 languages! :fire:
deoplete.nvim - :stars: Dark powered asynchronous completion framework for neovim/Vim8
fzf-lua - Improved fzf.vim written in lua
vim-repeat - repeat.vim: enable repeating supported plugin maps with "."
vim-commentary - commentary.vim: comment stuff out
nvim-bqf - Better quickfix window in Neovim, polish old quickfix window.