vim-ccls
vimspector
vim-ccls | vimspector | |
---|---|---|
6 | 100 | |
92 | 4,023 | |
- | - | |
0.0 | 8.0 | |
over 1 year ago | 2 days ago | |
Vim Script | Vim Script | |
MIT License | Apache License 2.0 |
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.
vim-ccls
- Vim-ccls: Vim plugin for the ccls language server
-
Getting neovim setup for C++ dev - CCLS
I've tried ccls.nvim and vim-ccls - any other recommendations?
-
State of the call hierarchy functionality
There is Litee's Calltree but I couldn't make it work. For C/C++, there is the Vim-Ccls plugin that adds those functionalities (although I don't like the UI). But in order to use it I had to switch from Clangd to Ccls and it broke the symbol tree of 2 plugins I had : Sidebar.nvim (which I actively used) and symbols-outline.nvim (an old plugin I tried to use again, but is broken by the change as well).
-
Extension like rust-tools.nvim, but for clangd (C & C++)
First I strip down ccls like this lua local cinit = function(client) require("mappings").nvim_lsp() local rc = client.resolved_capabilities rc.document_formatting = false rc.document_range_formatting = false rc.document_highlight = false rc.document_symbol = false rc.workspace_symbol = false rc.rename = false rc.hover = false rc.completion = false rc.code_action = false end require('lspconfig').ccls.setup{ on_init = cinit, handlers = { ["textDocument/publishDiagnostics"] = function(...) return nil end, ["textDocument/signatureHelp"] = function(...) return nil end, }, single_file_support = true, root_dir = Lsp.util.root_pattern("compile_commands.json", "compile_flags.txt", ".git"), } and then use vim-ccls for the AST extensions, config it with mappings.
-
GitHub - ldelossa/calltree.nvim: Neovim's missing call-hierarchy UI. (Help Test!!)
I use https://github.com/m-pilia/vim-ccls, and was hoping to find something more general. Thank you for making this.
-
Switching to nvim-lsp
you could go the route of writing your on handlers. I was incredibly lazy. there exists Martin Pilla' amazing plugin that does just that. All the hierarchy based jumps provided by ccls are inside that plugin.
vimspector
-
I can't stand using VSCode so I wrote my own (it wasn't easy)
There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.
- Shape Typing in Python
-
Certain Mapping only when another command was called earlier (lua)
I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).
-
Vimspector – the Vim debugger rules all
The actual title is "Vimspector - A multi-language debugging plugin for Vim".
It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...
-
How to configure vim like an IDE
vimspector
-
I like Tabasco.
I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.
-
Rust, RR, Neovim: A perfect debug combination
You could try vimspector. It's main target is vim and not neovim.
https://github.com/puremourning/vimspector/
-
Vim or Emacs for C++ Coding?
I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).
[0] https://github.com/ycm-core/YouCompleteMe
[1] https://github.com/puremourning/vimspector
[2] https://github.com/dense-analysis/ale
-
My office wants everyone to use vim as the only editor. Has this happened to anyone else?
For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.
What are some alternatives?
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
nvim-dap - Debug Adapter Protocol client implementation for Neovim
litee-calltree.nvim - Neovim's missing call hierarchy UI
nvim-gdb - Neovim thin wrapper for GDB, LLDB, PDB/PDB++ and BashDB
litee.nvim - A framework for building Neovim plugins
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
symbols-outline.nvim - A tree like view for symbols in Neovim using the Language Server Protocol. Supports all your favourite languages.
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
vim-yggdrasil - Vim library to generate tree-like views
ipdb - Integration of IPython pdb
dotfiles
omnisharp-roslyn - OmniSharp server (HTTP, STDIO) based on Roslyn workspaces