mirror of
https://github.com/GothenburgBitFactory/timewarrior.git
synced 2025-06-26 10:54:28 +02:00
b189ccb020
This replaces the generation of man pages on project setup by a on-demand generation via asciidoctor. An exception are the man pages for the commands `day`, `month`, and `week` which are simply redirects to the man page `timew-chart.1`. Those are now static files in the Timewarrior repository. A CMake find module to detect asciidoctor was added. If asciidoctor is found, the targets `doc`, `man1`, and `man7` are created. Those targets are also added to the default build target. If asciidoctor is not available, the target `doc` is available, but it only emits a message to install asciidoctor first. Signed-off-by: Thomas Lauf <thomas.lauf@tngtech.com>
30 lines
631 B
Text
30 lines
631 B
Text
= timew-ranges(7)
|
|
|
|
== NAME
|
|
timew-ranges - date and time ranges supported by Timewarrior
|
|
|
|
== SYNOPSIS
|
|
|
|
== DESCRIPTION
|
|
An interval defines a block of time that is tracked.
|
|
The syntax for specifying an interval is flexible, and may be one of:
|
|
|
|
[from] <date>
|
|
[from] <date> to/- <date>
|
|
[from] <date> for <duration>
|
|
<duration> before/after <date>
|
|
<duration> ago
|
|
[for] <duration>
|
|
|
|
Examples are:
|
|
|
|
from 9:00
|
|
from 9am - 11am
|
|
from 9:00:00 to 11:00
|
|
from 9:00 for 2h
|
|
2h after 9am
|
|
2h before 11:00
|
|
2h ago
|
|
for 2h
|
|
|
|
An interval is said to be 'closed' if there is both a start and end, and 'open' if there is no end date.
|