D22710: ensure clangd is started for each project on it's own

Christoph Cullmann noreply at phabricator.kde.org
Wed Jul 24 22:07:11 BST 2019

cullmann added a comment.

  Actually, I think the root issue is then that we started to mess with the compilationDatabasePath at all. (I guess I wanted that :)
  I did read the clangd docs (and tooling docs in general) again, too, and yes, you are right, I guess the symlink way is the one advertised and if I didn't want to use the build stuff from the project plugin, it would just work with one instance.

  R40 Kate


To: cullmann, dhaumann, mnauwelaerts
Cc: kwrite-devel, domson, michaelh, ngraham, demsking, cullmann, sars, dhaumann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwrite-devel/attachments/20190724/d8417df2/attachment.html>

More information about the KWrite-Devel mailing list