In case anyone is wondering why people use VSCode: I spent most of the day configuring LSP's for graybeard editors (vim/emacs) and God my head hurts!

@buherator hmm.. I do coding just as a hobby, so my setup is really just for my toy projects. That being said, I've actually had a positive experience setting up LSP support in vim. coc worked out of the box for me (yes, the dependency on node.js triggers me - but still better than vscode in my eyes)..

@hajovonta Apparently people did the implementation, but documentation is seriously lacking. Unfortunately I don't feel I have the experience to contribute, otherwise I'd just open PR's like crazy.

Do you happen to have a solution for Emacs to generate call hierarchies (func1--calls-->func2) without LSP?

@greg Maybe disqualifying coc because of node was a mistake on my end...

@hajovonta Yeah, I got into this because I want static tooling :/

@buherator well, it's disgusting. But it worked and I figured.. Well, as long as I don't have to interact with that JS stuff, it's still better than running that Electron junk.

What are you using?

@greg ccls.nvim worked best so far, but now I'm wrestling with Emacs where I expected components like the tree buffers to be better integrated. Now I'm stuck because the keys for file manipulation don't seem to work if the tree displays code elements :P