lsp
ctags
lsp | ctags | |
---|---|---|
26 | 33 | |
409 | 6,304 | |
- | 1.0% | |
8.8 | 9.7 | |
29 days ago | 6 days ago | |
Vim Script | C | |
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.
lsp
-
Vim 9 plugins
fuzzyy, lsp
-
LSP with pylsp: it work-ish but autocompletion and hover randomly work.
This issue https://github.com/yegappan/lsp/issues/305
-
Vim users who work without any plugins, how does your vimrc look like?
I think I remember that I have seen you over at https://github.com/yegappan/lsp so completely plugin less you aren't ;)
-
A micro plugin for highlighting yanked text in Vim9.
This plugin seems to have unit-test but I didn't dare to dig into it!
-
For conda users: a new(er) plugin to change environment inside Vim9.
To be honest I copied it from some of the completion functions that are defined in the LSP https://github.com/yegappan/lsp/
- ALE or lsp?
-
Recommended minimal set of plugins for a great experience
Lately I have looked into https://github.com/yegappan/lsp/ but is still falling back to good ol vim for renaming, showing references and completion.
-
Coc Is hogging a lot of memory, is it like this always? I only have 8 GB RAM, and I code a lot, do you guys have any suggestions and solutions on how I can make it a bit better?
I think that https://github.com/yegappan/lsp/ is OK, and the source code is easy to read, that's also why I have contributed to it.
- Lsp server for vim9?
-
install lsp in vim
Some language servers expects the client to filter completion items, others don't, and even others tell the client that it shouldn't filter the items. For the first case support for ignoredcase and fuzzy completion was merged a few days ago https://github.com/yegappan/lsp/pull/178
ctags
- If you owned a nvidia tesla a100, what would you do with it?
-
NeoVim & Rust
I also recommend you https://github.com/preservim/tagbar with https://ctags.io/ installed , it will map definitions (functions, enum, struct etc..) to tags and tagbar plugin allows you to open a split window with the mapped list and navigate through your file, it also enabled more advanced features for quick navigation .
-
How do you figure out which #include a function/variable came from?
grep, Ctags, Cscope, LSP
-
Vim plugin like vscode "go to definition" function
Vim has the tag feature built-in, which allows it to jump to the tags that were found by a tool like universal ctags using :h CTRL-]. See :help tags for more information on this. Fun fact: this is the approach that Vim uses when you use :help!
-
Neovim config from scratch (Part II)
Requirements: You need to have a CTags implementation like universal-ctags installed on your system (on every system where you use vim).
-
How to check the memory usage of my plugins?
Install https://github.com/universal-ctags/ctags
-
Project reading tools
If you are heavy Vim user, you do not need anything else. For just quick browsing, simply use ctags, make sure to use universal ctags (https://ctags.io) not exuberant ctags which are no longer well maintained. Go works out of box.
-
Help me set up vim for linting and a file tree please and some other stuff
Other (built-in) tools for file navigation in Vim include: :h :ls and :h :buffer to navigate in your buffer list (i.e. the files you have loaded); everything listed in [https://vimways.org/2018/death-by-a-thousand-files/](romainl's "Death by a Thousand Files" articles in vimways); using tags by installing universal-ctags to generate the tags then using any of the commands in :h tag to navigate them; setting global marks to files you use often with m[UPPERCASE LETTER] and jumping to them with `[UPPERCASE LETTER]; :h :vimgrep…
-
Ctags and referencing static functions, is it possible?
I have good news for you. Universal Ctags, an Exuberant Ctags fork and essentially its replacement, has fixed this already:
-
Searching files or words using fuzzy finders
Vim has built-in functionality that works pretty similar to what you want. If you have a tags file (for example, using universal ctags), you can hit Ctrl-] (:h Ctrl-]) to jump to the declaration of any function under your cursor. Or, if you don't have a tags file, you can use gd (:h gd) to jump to a local declaration within the open file.
What are some alternatives?
.vim - ✍️ Bootstrapping vim configuration for *nix systems
lsp-mode - Emacs client/library for the Language Server Protocol
vim9-scratchterm - Define a command, ScratchTerm, that creates a new terminal buffer and marks it as a scratch buffer. This allows us to kill all scratch terminals in the current view with a single function.
vscode-intelephense - PHP intellisense for Visual Studio Code
kamilscripts
nvim-lspconfig - Quickstart configs for Nvim LSP
vscode-ng-language-service - Angular extension for Visual Studio Code
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vim-conda-activate - Activate Conda environments in Vim.
vim-gutentags - A Vim plugin that manages your tag files
vim-lsp - async language server protocol plugin for vim and neovim
fzf.vim - fzf :heart: vim