Docs: Made raw notes more clearly separated

This commit is contained in:
Paul Beckingham 2016-03-13 15:40:39 -04:00
parent 719cfdf1b3
commit b02eaa1bcd
7 changed files with 12 additions and 8 deletions

View file

@ -124,6 +124,5 @@ A log entry will have this form:
YYYY-MM-DDTHH:MM:SS <version> <category> <message>
---
--- Raw Notes ---

View file

@ -137,8 +137,8 @@ Will construct the rule like this:
The process of converting this rule structure to 'one.two.three four' is called
normalizing.
---
--- Raw Notes ---
By using tags, this becomes:

View file

@ -119,4 +119,5 @@ supported keywords are:
:quiet No feedback
:x User defined
---
--- Raw Notes ---

View file

@ -83,5 +83,6 @@ Or the data can be exported in JSON:
$ timew export last month > February.json
---
--- Raw Notes ---

View file

@ -102,7 +102,8 @@ Extensions
----------
A simple extension mechanism allows custom reports to be written and shared.
---
--- Raw Notes ---
- Given this:
$ timew track yesterday 9am - 5pm tag1

View file

@ -80,7 +80,8 @@ That is, the input it line-oriented, with first a header block of name/value
pairs, then a blank line, then the JSON filtered data. The header block has all
configuration names flattened, i.e. no hierarchy.
---
--- Raw Notes ---
- The Taskwarrior hook script should use a set of attributes for time tracking
tags. Those will include: UUID, project, tags, description, and any chosen UDAs.

View file

@ -194,7 +194,8 @@ There are several built-in functions, which may be used by rules:
log("...") Logs and continues
sum_week("tag1") Sums minutes in the current week for "tag1"
---
--- Raw Notes ---
- Need to distinguish between regular time and over time, with different rates
and limits.