Files

ryneeverett 0944c73716 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.

2024-04-16 08:19:58 -04:00

devel

Recommend LSP's in development docs (#3370 )

2024-04-16 08:19:58 -04:00

man

Check that sync.server.origin is a URL (#3361 )

2024-04-16 02:11:55 +00:00

holidays: Update for 2022

2021-10-01 21:59:00 -04:00

ref

Update copyright to 2020

2020-11-21 12:27:05 -05:00

CMakeLists.txt

Use corrosion instead of CMakeRust (#3273 )

2024-03-02 16:21:34 -05:00

README.md

Better links from TW devel docs to TaskChampion (#3253 )

2024-01-21 18:03:11 -05:00

README.md

Documentation

This directory contains Taskwarrior documentation that is built and installed along with the executable:

man contains the source for the Taskwarrior manual pages.
rc contains rcfiles that will be installed in /usr/share/doc/task/rc or equivalent.
ref contains reference documentation that will be installed in /usr/share/doc/task or equivalent.

It also contains developer documentation with a high-level view of how Taskwarrior development is done and how the pieces of the system fit together.