Recommend LSP's in development docs (#3370)

* Recommend LSP's in development docs

Per conversation in #3338.

There are already a lot of documented compile options so I think we're
better off suggesting that everybody create a compile_commands.json
whether or not they're using an LSP because it doesn't cost much.

While I was at it it seemed reasonable to mention rust LSP too. Now that
rls is deprecated I'm not sure there is any competitor to rust-analyzer
worth mentioning.

* Export compile commands by default.

Thanks to @felixschurk for the idea and telling me how to do it.

It took me a minute to figure out that this places the
compile_commands.json in the build directory rather than the root of the
project. But clangd still finds it there and that's a better place for
it anyway.
This commit is contained in:
ryneeverett
2024-04-16 08:19:58 -04:00
committed by GitHub
parent 10cec507cb
commit 0944c73716
2 changed files with 8 additions and 2 deletions

View File

@@ -1,5 +1,7 @@
cmake_minimum_required (VERSION 3.22)
set (CMAKE_EXPORT_COMPILE_COMMANDS ON)
project (task
VERSION 3.0.0
DESCRIPTION "Taskwarrior - a command-line TODO list manager"