mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-06-26 10:54:26 +02:00
0944c73716
* 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. |
||
|---|---|---|
| .. | ||
| contrib | ||
| rfcs | ||
| README.md | ||
Development Documentation
This directory contains the development documentation for Taskwarrior. For all other documenation, see https://taskwarrior.org.
Taskwarrior and TaskChampion
As of the 3.0 release, Taskwarrior uses TaskChampion to manage task data. Find documentation of TaskChampion here:
- TaskChampion README
- TaskChampion CONTRIBUTING guide
- TaskChampion Book
- TaskChampion API Documentation
TaskChampion will become its own project soon.