`tim` is intended as a quick support alias for timewarrior.
If invoked without any arguments, `tim` will print out a simple summary
of all tasks accomplished (for the day by default). It will also print
their ids for simple subsequent modification tasks.
If, however, invoked with additional arguments, `tim` will pass anything
along to timewarrior so anything happens as usual if invoked like this.
Thus, `tim` functions as a quick look into the day's timesheet or a
shorter alternative to the `timew` command.
Timewarrior now looks for its data directory in `XDG_CONFIG_HOME`
instead of the home directory. This is a little better than nothing, but
does not separate the configuration and data files from each other yet.
Data *should* be lying in `XDG_DATA_HOME` but the data directory can not
be separated since it relies on a single env var `TIMEWARRIORDB`.
Fixed error in configuration file location for taskopen alias which put
the config file instead of the notes directory.
Now configuration file correctly resides in
$XDG_CONFIG_HOME/task/taskopenrc and notes dir is
$XDG_DATA_HOME/task/notes.
Notes can now correctly be created by doing `task <id> annotate Note`.
Fixed the completions for the `t` alias that takes over task
functionality on the shell. Only works on zsh, and presumably not on
every system since it relies on some ps trickery to find out the
currently running shell. Maybe there's a better version out there
somewhere...
Added basic distinction into work/personal contexts, since, with my
current job having a complex enough task list I want that either not
cluttering up my enjoyable tasks, or *only* that cluttering up all my
tasks.
To use taskwarrior, an alias to `t` has been created. If you invoke any
taskwarrior command through `t`, it will behave just as taskwarrior
would (just with a shorter name).
If you invoke `t` without any additional arguments, it will instead open
up the tasksh program and let you play around in there.
Marty Oehme