neo-runner.nvim
kok.nvim
neo-runner.nvim | kok.nvim | |
---|---|---|
1 | 60 | |
9 | 3,368 | |
- | - | |
5.0 | 9.3 | |
about 3 years ago | 7 days ago | |
Python | Python | |
- | 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.
neo-runner.nvim
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?
neovim-cmake - CMake integration for Neovim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
gdoc.vim - Google docs integration for vim
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.
chadtree - File manager for Neovim. Better than NERDTree.
nvim-cmp - A completion plugin for neovim coded in Lua.
deoplete-jedi - deoplete.nvim source for Python
deoplete.nvim - :stars: Dark powered asynchronous completion framework for neovim/Vim8
semshi - 🌈 Semantic Highlighting for Python in Neovim
vim-repeat - repeat.vim: enable repeating supported plugin maps with "."
nvim-bqf - Better quickfix window in Neovim, polish old quickfix window.
ultisnips - UltiSnips - The ultimate snippet solution for Vim. Send pull requests to SirVer/ultisnips!