Task recognizes several entries in the .taskrc file for
configuration purposes. Valid entries are of the form:
name=value
Valid examples are:
data.location
This is a path to the directory containing all the task files.
By default, it is set up to be ~/.task, for example:
/Users/paul/.task
command.logging
May be "on" or "off", defaulting to "off". This determines
whether task records commands. This is not generally useful,
except while developing task.
confirmation
May be "yes" or "no", and determines whether task will ask for
confirmation before deleting a task.
nag
This may be a string of text, or blank. It is used as a prompt
when a task is completed that is not considered high priority.
The "task next" command lists important tasks, and completing
one of those does not generate this nagging. Default value is:
Note: try to stick to high priority tasks. See "task next".
next
Is a number, defaulting to 2, which is the number of tasks for
each project that are shown in the "task next" command.
curses
Determines whether task uses ncurses to establish the size of
the window you are using, for text wrapping.
blanklines
May be "on" or "off". Prevents the display of unnecessary blank
lines so that task makes better use screen real estate on small-
screened devices.
dateformat
This is a string of characters that define how task formats dates.
The default value is:
m/d/Y
which means dates look like:
6/7/2008
The string should contain the characters:
| Character |
Meaning |
Example |
| m |
minimal-digit month |
1, 12 |
| d |
minimal-digit day |
1, 30 |
| y |
two-digit year |
08 |
| M |
two-digit month |
01, 12 |
| D |
two-digit day |
01, 30 |
| Y |
four-digit year |
2008 |
The string may also contain other characters to act as spacers,
or formatting. Other values could include (but are not limited to):
| dateformat
| How it looks |
| d/m/Y |
7/6/2008 |
| YMD |
20080607 |
| m-d-y |
6-7-08 |
showage
May be "yes" or "no". Determines whether the "Age"
column appears on the "list" and "next" reports.
monthsperline
Determines how many months the "task calendar" command
renders across the screen. Defaults to 1.
oldest
Determines how many tasks the "task oldest" command displays.
Defaults to 10.
newest
Determines how many tasks the "task newest" command displays.
Defaults to 10.
defaultwidth
The width of tables used when ncurses support is not available.
Defaults to 80.
color
May be "on" or "off". Determines whether task uses color.
When "off", task will use dashes (-----) to underline column
headings.
color.overdue
color.due
color.pri.H
color.pri.M
color.pri.L
color.pri.none
color.active
color.tagged
These are the coloration rules. They correspond to a particular
attribute of a task, such as it being due, or being active, and
specifies the automatic coloring of that task. The value may
be one optional foreground color (see below) and one optional
background color. For example, the value may be:
bold_red on_bright_yellow
color.tag.X
Colors any task that has the tag X.
color.project.X
Colors any task assigned to project X.
color.keyword.X
Colors any task where the description contains X.
default.project
Provides a default project name for the "task add ..." command.
default.priority
Provides a default priority for the "task add ..." command.
default.command
Provides a default command that is run every time task is
invoked with no arguments. For example, if set to:
default.command=list project:foo
Then task will run the "list project:foo" command if no
command is specified. This means that by merely typing:
% task
[task list project:foo]
ID Project Pri Description
1 foo H Design the thing
2 foo Build the thing
Note that the value of this variable is simply the command
line that you would ordinarily type, but without the
preceding "task" program name.
Copyright 2006-2008, P. Beckingham. All rights reserved.