mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-06-26 10:54:26 +02:00
Documentation
- Fixed typos.
This commit is contained in:
parent
837b89dd2d
commit
6de940acf1
2 changed files with 13 additions and 12 deletions
|
@ -1425,9 +1425,9 @@ For a general dark theme:
|
|||
include /usr/local/share/doc/task/rc/dark-256.theme
|
||||
.RE
|
||||
|
||||
Here are two color rules that specifies a dark blue background for all tasks
|
||||
that are part of the 'party' project, and uses bold to identify any tasks with
|
||||
the keyword 'invitations' in the description.
|
||||
Here are two color rules that specify a dark blue background for all tasks that
|
||||
are part of the 'party' project, and uses bold to identify any tasks with the
|
||||
keyword 'invitations' in the description.
|
||||
|
||||
.RS
|
||||
$ task "rc.color.project.party=on rgb001" rc.color.keyword.invit=bold list
|
||||
|
@ -1534,8 +1534,8 @@ ID Project Pri Due Active Age Description
|
|||
.RE
|
||||
|
||||
.SH DUE DATES
|
||||
Due dates can be specified as dates, durations into the future or past, by
|
||||
mnemonic, ordinal of day of week.
|
||||
Due dates can be specified as dates, durations into the future or past,
|
||||
mnemonic, ordinal or day of week.
|
||||
|
||||
.RS
|
||||
$ task 1 due:7/31/2010
|
||||
|
@ -3409,9 +3409,10 @@ Imported 1 tasks successfully, with 0 errors.
|
|||
.RE
|
||||
|
||||
Here is a YAML example. Taskwarrior can read several formats, including old
|
||||
versions task data. Using YAML, you can round-trip the data without loss, which
|
||||
means you can export and import without any missing information. This also
|
||||
means that 'export.yaml' is good for making a backup copy of your tasks.
|
||||
versions of its data files. Using YAML, you can round-trip the data without
|
||||
loss, which means you can export and import without any missing information.
|
||||
This also means that 'export.yaml' is good for making a backup copy of your
|
||||
tasks.
|
||||
|
||||
.RS
|
||||
$ cat file.yaml
|
||||
|
|
|
@ -238,7 +238,7 @@ task list
|
|||
vi ~/.taskrc
|
||||
task list
|
||||
|
||||
Here is a color rule that specifies a dark blue
|
||||
Here is are two color rules that specify a dark blue
|
||||
background for all tasks that are part of the 'party'
|
||||
project, and uses bold to identify any tasks with the
|
||||
keyword 'invitations' in the description.
|
||||
|
@ -273,7 +273,7 @@ task 1 due:2wks as some distance into the future...
|
|||
task 1 due:-2wks or past...
|
||||
task 1 due:eom or by mnemonic (end of month)...
|
||||
task 2 due:8th or by ordinal...
|
||||
task 2 due:sunday or by day...
|
||||
task 2 due:sunday or by day of week...
|
||||
task 5 due:eow
|
||||
task list Some of these dates are in the past, so now you see there
|
||||
task overdue are overdue tasks. Due dates have different colors for
|
||||
|
@ -500,8 +500,8 @@ cat file.text I can also import. Here I am importing
|
|||
task import file.text text. Taskwarrior recognizes the format and confirms.
|
||||
|
||||
cat file.yaml Here is a YAML example. Taskwarrior can read several
|
||||
task import file.yaml formats, including old versions task data. Using YAML,
|
||||
you can round-trip the data without loss.
|
||||
task import file.yaml formats, including old versions of its data files. Using
|
||||
YAML, you can round-trip the data without loss.
|
||||
|
||||
task new limit:2 Here are the imported tasks.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue