Custom note extensions can be set and opened through annotating a task
with `Note.ext` instead of just the usual `Note` - the extension will
automatically be opened.
Additionally, tasks annotated with links can now have their links opened
through xdg-open with `to`.
Added aliases for task adding (`ta`), logging (`tal`), annotating (`tan`);
listing next upcoming (`tn`), listing next urgent (`tun`);
showing active (`tra`) and getting a report of recently (1 week)
completed (`trw`) and, finally, `to` to invoke taskopen on the task
passed in.
Added alias within taskwarrior to invoke taskopen through
(unsurprisingly) `task open`. Importantly, the difference to other
taskwarrior commands is that the number of the task to open should come
AFTER the command, not before as a filter as for all the others. Perhaps
that can be changed in the future.
There are some includes in taskwarrior which make the program error out
if they don't exist on start. This little hook ensures that they get
created each time a new environment is created.
Up to now tasks that were blocking other tasks would just get a bump in
urgency in taskwarrior. Vice versa for tasks being blocked.
However, this could still lead to situations in which a task A blocking
task B would appear in the list (sorted by urgency) BEHIND task B. If
one task is blocking another, I can not reasonably assume to be able to
complete the one blocked, right?
So this lead to more confusion that anything and now, any task that
blocks another task simply inherits its urgency, appearing directly
before the other task in the list. Should solve the problem, though they
may not be able to receive their own urgencies anymore, should that be
important.
Updated the formatting of the taskopen configuration file to conform to
its new display.
Updated the xdg-conforming `taskopen` alias to use long-form option
since the short-form option seems bugged at the moment.
Added hook starting and stopping timewarrior tracking whenever starting,
stopping or completing a task in taskwarrior.
Really nice script, robust as well for starting multiple tasks and
start/stopping intermittently.
Prepared dunst config for using the newly introduced (v1.8.0) drop-in
configuration files. This allows spreading out dunst configuration over
arbitrary files in the `dunstrc.d/` folder in the usual configuration
folder. Will be perfect for less intrusive `styler` changes.
Added icons to be displayed on dunst notifications if there are any.
Also prepared zathura configuration in a similar way, with the
configuration file containing an include directive for a colorscheme
file.
Lastly, moved taskwarrior theme options into their own file and included
them with an include directive.
Here, the file itself needs to be committed as well since taskwarrior
will complain about missing file being included otherwise. However, we
simply ignore the file in git after force-including it and no changes
will be tracked.
This means that from now on, styler theme changes should not show up as
uncommitted changes in the repository anymore for currently active
programs.
Fixes#6.
Added simple script `task-overdue-prompt` which checks for overdue tasks
(*not* tasks to be done 'today') and display a skull if there are any.
Intended for prompt use, it is currently still too slow to be used as
such. But there may still be uses other than that so it is included for now.
`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`.
Removed nagscreen informing of 2.6.0 news that would periodically tell
you about 'new' things in taskwarrior by telling it i already saw it.
Removed perviously added auto-sync function. Two reasons:
The individual additions/modifications in taskwarrior take longer if
they need to be communicated to a server at the end of every change.
And undo does not work at all if we are already syncing to a server
after every change.
That means wrong changes are also synced and become really hard to
remove again.
So, it seems easier to, for now, sync manually after some commands and
before leaving one workstation for another. Another method of auto-sync
could be implemented but I have not found an elegant way.
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`.
Now silently syncs in the background instead of blocking input. *May*
produce zombie processes in rare circumstances? Will need to investigate
it some more.
Behind the scenes, the shell script has been replaced by a python script
which creates a (disowned) background process which attempts the
syncing.
Let taskwarrior automatically sync any changed tasks whenever a process
is completed.
Will sync 'asynchronously' (start the job as a terminal background
process) and show the sync message after it is done.
Added a report to look at the tasks I completed over the past day,
invoked by `today.completed`. The name was chosen to interact well with
my `today` overview report which shows the remaining tasks.
Also defaulted to the built-in solarized dark theme since it seems to
work best with a variety of color schemes -- and since I switch
frequently using styler, it makes sense to default to this one.
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.
Added freecinc target for syncing tasks over the web.
Using freecinc is easy and relatively painless, which is why, for now,
this is the syncing server I have chosen.
Once the taskwarrior workflow in this setup matures and stabilizes a bit
the syncing target should undoubtedly move to a self-hosted instance of
taskserver, ideally encrypted.
Until then, the tasks currently available will exist *unencrypted* on
the freecinc server.
Simple today report added, mimicking the overall next report list (i.e.
sorted by urgency), but only focusing on things due today. This reflects
my setup in Todoist a bit better, and should perhaps provide a bit of a
crutch until I get more used to the taskwarrior way of doing things.
Additionally, added a simple fix for the annoying tendency of
taskwarrior to add today's tasks to its overdue list.
This happens because tasks added without a specific time will be added
as due at the very *first* minute of a day (instead of e.g. at the very
last, every task needs an exact time).
This simply removes tasks due today from overdue reports.
This is not perfect! Two things remain: Tasks still carry the virtual
`+OVERDUE` tag around with them, and those tags that actually should be
done at a certain time during the day will also not be shown in the
overdue report - though they definitely are overdue then.
A possible workaround for the second issue is the taskwarrior hook here:
https://gitlab.com/marty-oehme/dotfiles/-/snippets/2054237
But, I am happy enough with the setup as-is for now, without
complicating it with the hook.
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.
