or just use #ccls instead of #clangd :D

In diesem Jahr findet zum zweiten Mal die Joanna-Conference, die Konferenz für Computational Literary Studies statt. Wir freuen uns natürlich besonders, dass sie quasi in unserer Nachbarschaft in Würzburg ausgerichtet wird ☺️🌻 Mehr darüber heute und morgen hier! #CCLS

@suprjami
`make --dry-run` prints but doesn't run the commands. Bear wraps the compiler calls to intercept them, so it requires you to actually call the compiler.

The whole problem is that there's no way to get the includes and dependencies unless you do all the preprocessing, which is a portion of the way into compiling. You could add the compiler flag to only do pre-processing, but you'll only save a little time versus a full compile.

#cprogramming #gcc #clang #llvm #ccls

I really wish there was a Makefile way to generate compile_commands.json without running an actual build. Bear doesn't catch the output of "make --dry-run". This really feels like it should be a solved problem already? #CProgramming #GCC #Clang #LLVM #ccls

Is it just me, or is there no way to use clangd with the Linux Kernel without doing an entire build to generate compile_commands.json? I don't have hours to wait for a build every time I switch git branches, which I do very often. Just opening random files with vim-lsp and clangd setup for C files doesn't work well. #clangd #ccls #lsp #llvm #kernel

Turns out if you setup vim-lsp with ccls and open a directory with C it... just magically works! No compilation database necessary. Having used this for a couple of days on userspace projects and libraries like SDL2, I can see why people really like this. #Vim #Neovim #LSP #ccls #clangd #CProgramming

@merazi@hostux.social did some really quick testing and #clangd bugged out almost immediately 🙄

Using #ccls for now. No issues so far.

Switching from #cedet+#semantic to #lsp. Looking good so far!

But should I use #ccls or #clangd?

#emacs

Struggling a bit with #ccls in #openframeworks... The language server refuses to recognize ofMain.h, even though its directory is dutifully listed in compile_commands.json... Anybody have any experience with getting cpp and openframeworks behave appropriately?