The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Vim-ccls Alternatives
Similar projects and alternatives to vim-ccls
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
symbols-outline.nvim
Discontinued A tree like view for symbols in Neovim using the Language Server Protocol. Supports all your favourite languages.
-
ccls
C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
ale
Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
-
ccls.nvim
Neovim plugin for ccls language server. Leverages off-spec extensions to LSP client with AST browser
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
vim-ccls reviews and mentions
- 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.
-
A note from our sponsor - WorkOS
workos.com | 27 Apr 2024
Stats
m-pilia/vim-ccls is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of vim-ccls is Vim Script.
Sponsored