Marty/dotfiles
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Wiki Activity
dotfiles/taskwarrior/.config/task/taskrc

76 lines
3.1 KiB
Text
Raw Normal View History

taskwarrior: Add basic taskrc file
2020-12-25 10:57:31 +00:00
# Taskwarrior program configuration file.
# For more documentation, see http://taskwarrior.org or try 'man task', 'man task-color',
# 'man task-sync' or 'man taskrc'
# Here is an example of entries that use the default, override and blank values
# variable=foo -- By specifying a value, this overrides the default
# variable= -- By specifying no value, this means no default
# #variable=foo -- By commenting out the line, or deleting it, this uses the default
# Use the command 'task show' to see all defaults and overrides
# Files
data.location=~/.local/share/task
# disable case sensitivity
search.case.sensitive=no
# german-style week start
weekstart=monday
# Make daily burndown default alias
alias.burndown=burndown.daily
# Sort the columns a little differently
active.indicator=>
taskwarrior: Add today report, fix overdue report 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.
2020-12-25 16:56:58 +00:00
taskwarrior: Add basic taskrc file
2020-12-25 10:57:31 +00:00
# customize list report: focus on due dates
report.list.columns=start.active,id,project,priority,due,description,tags,entry.age
report.list.labels=,,Project,Pri,Due,Description,Tags,Age
# customize next report: focus on urgencies
report.next.columns=id,project,priority,urgency,due,description,tags,scheduled,entry.age,recur
report.next.labels=,Project,Pri,Urg,Due,Description,Tags,Sched,Age,Recur
taskwarrior: Add today report, fix overdue report 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.
2020-12-25 16:56:58 +00:00
# customize overdue report: hide tasks which are due today, but scheduled for 00:00:00
report.overdue.filter=(status:pending or status:waiting) and +OVERDUE and -TODAY
# custom today report, sorted by urgency
report.today.filter=status:pending +TODAY limit:page
report.today.sort=urgency-
report.today.columns=id,project,priority,urgency,due,description,tags,scheduled,entry.age,recur
report.today.labels=,Project,Pri,Urg,Due,Description,Tags,Sched,Age,Recur
taskwarrior: Add basic taskrc file
2020-12-25 10:57:31 +00:00
# reorder priorities so that explicitly tagged 'Low' items are lower than normal
uda.priority.values=H,M,,L
urgency.uda.priority.L.coefficient=0
urgency.uda.priority..coefficient=1.8
# Just because its tagged/annotated doesn't mean its important
urgency.tags.coefficient=0
urgency.annotations.coefficient=0
# only ever show one result in the task shell
tasksh.autoclear=1
taskwarrior: Add taskserver sync target 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.
2021-02-19 08:47:57 +00:00
# temporary taskd configuration for freecinc (should be selfhosted at some point)
taskd.server=freecinc.com:53589
taskd.key=~/.local/share/task/keys/freecinc_7ebc40a3.key.pem
taskd.certificate=~/.local/share/task/keys/freecinc_7ebc40a3.cert.pem
taskd.ca=~/.local/share/task/keys/freecinc_7ebc40a3.ca.pem
taskd.credentials=FreeCinc\/freecinc_7ebc40a3\/1b2f5c1e-3d62-4a35-82c8-82ce0e23731e
taskwarrior: Add basic taskrc file
2020-12-25 10:57:31 +00:00
# Color theme (uncomment one to use)
#include /usr/share/doc/task/rc/light-16.theme
#include /usr/share/doc/task/rc/light-256.theme
#include /usr/share/doc/task/rc/dark-16.theme
#include /usr/share/doc/task/rc/dark-256.theme
#include /usr/share/doc/task/rc/dark-red-256.theme
#include /usr/share/doc/task/rc/dark-green-256.theme
#include /usr/share/doc/task/rc/dark-blue-256.theme
#include /usr/share/doc/task/rc/dark-violets-256.theme
#include /usr/share/doc/task/rc/dark-yellow-green.theme
#include /usr/share/doc/task/rc/dark-gray-256.theme
#include /usr/share/doc/task/rc/dark-gray-blue-256.theme
#include /usr/share/doc/task/rc/solarized-dark-256.theme
#include /usr/share/doc/task/rc/solarized-light-256.theme
#include /usr/share/doc/task/rc/no-color.theme
Reference in a new issue Copy permalink