mirror of
https://github.com/GothenburgBitFactory/timewarrior.git
synced 2025-07-07 20:06:39 +02:00
Docs: Combined example notes
This commit is contained in:
parent
76c31c094f
commit
506fe5c97c
1 changed files with 5 additions and 26 deletions
|
@ -1,7 +1,11 @@
|
|||
Use Cases
|
||||
=========
|
||||
Simplest usage, as a clock:
|
||||
|
||||
Basic usage summary:
|
||||
$ timew start
|
||||
$ timew stop
|
||||
|
||||
This uses a 'default' tag. By using tags, this becomes:
|
||||
|
||||
$ timew start tag1 # Start tracking now
|
||||
$ timew start "Home Improvement Project" # Stop old interval, start new interval now
|
||||
|
@ -69,28 +73,3 @@ associated metadata:
|
|||
|
||||
---
|
||||
|
||||
P: So the first six lines of examples show timew in use without any exclusions. That just turns it into a stopwatch.
|
||||
F: yes.
|
||||
P: But when you add exclusions, you get to say “timew track monday tag1” and it does something less than 24 hours.
|
||||
You also get to use fill.
|
||||
F: Right.
|
||||
|
||||
|
||||
F: I like the rules for days.
|
||||
Referring to the past.
|
||||
P: Yes, I think that makes sense.
|
||||
F: Do we want to have “modifiers” for this?
|
||||
P: How so?
|
||||
F: timew track last week mon - wed tag1
|
||||
or
|
||||
timew track mon - wed last week tag1
|
||||
P: Yes, we do, but I would prefer this:
|
||||
timew track last week monday - last week wednesday tag1
|
||||
F: Yes.
|
||||
P: Maybe we’ll find a better way to do this, but we need to be able to do all kinds of weird things with dates:
|
||||
last monday, this monday, next monday, monday
|
||||
F: Would this here ever happen?
|
||||
timew track last week tag1
|
||||
P: yes
|
||||
That’s an auto-fill if you have exclusions.
|
||||
F: tag1 = vacation on the island
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue