mirror of
https://github.com/GothenburgBitFactory/taskwarrior.git
synced 2025-06-26 10:54:26 +02:00
Spell checking on man pages
This commit is contained in:
parent
d45ce09ccc
commit
466cc4c362
3 changed files with 11 additions and 11 deletions
|
@ -105,7 +105,7 @@ confirmation=yes
|
||||||
.br
|
.br
|
||||||
to have a value of "no".
|
to have a value of "no".
|
||||||
|
|
||||||
While the use of projects and priorities are not essential to benefitting
|
While the use of projects and priorities are not essential to benefiting
|
||||||
from task, they can be very useful when the list of tasks grows large.
|
from task, they can be very useful when the list of tasks grows large.
|
||||||
Let's assign a project to these tasks:
|
Let's assign a project to these tasks:
|
||||||
.br
|
.br
|
||||||
|
|
|
@ -7,7 +7,7 @@ task \- A command line todo manager.
|
||||||
.B task [subcommand] [args]
|
.B task [subcommand] [args]
|
||||||
|
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
Task is a command line TODO list manager. It maintains a list of tasks that you
|
Task is a command line todo list manager. It maintains a list of tasks that you
|
||||||
want to do, allowing you to add/remove, and otherwise manipulate them. Task
|
want to do, allowing you to add/remove, and otherwise manipulate them. Task
|
||||||
has a rich list of subcommands that allow you to do various things with it.
|
has a rich list of subcommands that allow you to do various things with it.
|
||||||
|
|
||||||
|
@ -133,7 +133,7 @@ Shows the long usage text.
|
||||||
.SH REPORT SUBCOMMANDS
|
.SH REPORT SUBCOMMANDS
|
||||||
|
|
||||||
A report is a listing of information from the task database. There are several
|
A report is a listing of information from the task database. There are several
|
||||||
reports currently predefined in task. The output and sort behaviour of these
|
reports currently predefined in task. The output and sort behavior of these
|
||||||
reports can be configured in the configuration file. See also the man page taskrc(5).
|
reports can be configured in the configuration file. See also the man page taskrc(5).
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
|
@ -388,10 +388,10 @@ $ task add -- project:Home needs scheduling
|
||||||
|
|
||||||
.SH CONFIGURATION FILE AND OVERRIDE OPTIONS
|
.SH CONFIGURATION FILE AND OVERRIDE OPTIONS
|
||||||
Task stores its configuration in a file in the user's home directory:
|
Task stores its configuration in a file in the user's home directory:
|
||||||
~/.taskrc . The default configuration file can be overriden with
|
~/.taskrc . The default configuration file can be overridden with
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B task rc:<pathi-to-alternate-file>
|
.B task rc:<path-to-alternate-file>
|
||||||
Specifies an alternate configuration file.
|
Specifies an alternate configuration file.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
|
|
|
@ -26,7 +26,7 @@ attribute when running task:
|
||||||
$ task rc:<directory-path>/.taskrc
|
$ task rc:<directory-path>/.taskrc
|
||||||
.RE
|
.RE
|
||||||
|
|
||||||
Individual option can be overriden by using the
|
Individual option can be overridden by using the
|
||||||
.I rc.<name>:
|
.I rc.<name>:
|
||||||
attribute when running task:
|
attribute when running task:
|
||||||
|
|
||||||
|
@ -113,7 +113,7 @@ May be "yes" or "no", and determines whether task will ask for confirmation befo
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B echo.command=yes
|
.B echo.command=yes
|
||||||
May be "yes" or "no", and causes task to display the ID and description of any task when you run the start, stop, do, undo, delete and undelete commands. The default value is "yes".
|
May be "yes" or "no", and causes task to display the ID and description of any task when you run the start, stop, do, undo or delete commands. The default value is "yes".
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B next=2
|
.B next=2
|
||||||
|
@ -196,7 +196,7 @@ use dashes (-----) to underline column headings.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B fontunderline=on
|
.B fontunderline=on
|
||||||
Determines if font underlines or ascii dashes should be used to underline
|
Determines if font underlines or ASCII dashes should be used to underline
|
||||||
headers.
|
headers.
|
||||||
|
|
||||||
Task has a number of coloration rules. They correspond to a particular attribute
|
Task has a number of coloration rules. They correspond to a particular attribute
|
||||||
|
@ -375,7 +375,7 @@ The description for report X when running the "task help" command.
|
||||||
.B report.X.columns
|
.B report.X.columns
|
||||||
The columns that will be used when generating the report X. Valid columns are:
|
The columns that will be used when generating the report X. Valid columns are:
|
||||||
id, uuid, project, priority, entry, start, due, recur, recur_ind, age, age_compact,
|
id, uuid, project, priority, entry, start, due, recur, recur_ind, age, age_compact,
|
||||||
active, tags, description, description_only. The IDs are seperated by commas.
|
active, tags, description, description_only. The IDs are separated by commas.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B report.X.labels
|
.B report.X.labels
|
||||||
|
@ -385,7 +385,7 @@ are a comma separated list.
|
||||||
.TP
|
.TP
|
||||||
.B report.X.sort
|
.B report.X.sort
|
||||||
The sort order of the tasks in the generated report X. The sort order is specified
|
The sort order of the tasks in the generated report X. The sort order is specified
|
||||||
by using the column ids postfixed by a "+" for ascending sort order or a "-" for
|
by using the column ids post-fixed by a "+" for ascending sort order or a "-" for
|
||||||
descending sort order. The sort IDs are separated by commas
|
descending sort order. The sort IDs are separated by commas
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue