mirror of
https://github.com/GothenburgBitFactory/timewarrior.git
synced 2025-07-07 20:06:39 +02:00
Docs: Added notes
This commit is contained in:
parent
aff4b5133f
commit
d27ae7bd73
3 changed files with 7 additions and 1 deletions
|
@ -277,3 +277,7 @@ associated metadata:
|
|||
|
||||
$ timew start tag1 :fill inc 9:30am - # tag
|
||||
|
||||
- Need example and handling for people with exclusions that are not based on a
|
||||
seven-day cycle. Example, I have have every other friday off. This should be
|
||||
a supported exclusion, not 26 exceptions.
|
||||
|
||||
|
|
|
@ -34,6 +34,8 @@ Non-Goals
|
|||
- No explicit multi-user support, although using tags to track individuals is
|
||||
possible.
|
||||
- There is no hook system as Timewarrior is a data sink, not a data source.
|
||||
That said, there will be rules that can act as hooks, but will be more
|
||||
flexible.
|
||||
- No features without a compelling use case.
|
||||
|
||||
|
||||
|
|
|
@ -163,7 +163,7 @@ of the configuration files:
|
|||
|
||||
name = value
|
||||
|
||||
The hierarchy and 'configuration' rule will suupercede these.
|
||||
The hierarchy rule will supercede these.
|
||||
|
||||
|
||||
Rule Type: Theme
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue