emacs-for-vimmers VS emacs-ccls

git clone https://github.com/ideasman42/emacs-for-vimmers

Suggest to start off with a small vim-like config if doom or spacemacs aren't for you (see emacs-for-vimmers).

I prefer not to depend on any existing frameworks, here is the emacs/VIM config I wish I had starting out - minimal & commented: emacs-for-vimmers

If you don't want a starter kit - but are interested in a commented vim-like setup, checout: emacs-for-vimmers. Even if you are not into VIM, the defaults may be of interest to you.

I came from a fairly similar place, this is a fairly minimal package set to have a useful evil-mode up and running: https://github.com/ideasman42/emacs-for-vimmers

This is a fully self contained config made by making minor changes to emacs-for-vimmers that works in my tests.

If you'd like to have a reference for a lite weight vim/emacs setup, checkout https://github.com/ideasman42/emacs-for-vimmers - for a commented configuration that gets you up and running without having to buy into a framework.

Suggest https://github.com/ideasman42/emacs-for-vimmers to get you up and running with something approximating a typical development configuration in VIM.

Check packages used by emacs-for-vimmers - the config file is short and commented, giving a minimal VIM-like setup that includes features useful to developers.

If you like building your own config from scratch - check out emacs-for-vimmers as a reference.

ccls with lsp-mode and dap-mode and is what will fill most of those needs.

I haven't written any decent elisp code for ~3 years now and admittedly I have forgotten the little elisp knowledge I used to have. Upgrading doom-emacs has been a challenge for me as I'd be difficult to deal with possible breakage. (Also, sorry to admit that but I have also shifted some editor usage to neovim.) I am not able to properly maintain https://github.com/MaskRay/emacs-ccls anymore. There has been a few client-side issues I would probably never know how to address.

I've broken into emacs backtrace with kill -USR2 and I've dumped the lsp io log, and what I can tell is that there's no communication between ccls and emacs when the hang happens. This isn't a case of ccls flooding emacs. The backtrace shows that its hanging on this line of ccls-mode: https://github.com/MaskRay/emacs-ccls/blob/master/ccls-semantic-highlight.el#L304 Specifically its hanging inside that call to find-buffer-visiting in some tramp internals. What I'm wondering is, is ccls-mode misusing this call? Or is something broken in tramp?