Documentation

- Update the man page with the correct description of behaviour of
  rc.confirmation and rc.bulk variables
This commit is contained in:
Tomas Babej 2015-01-22 09:11:02 +01:00 committed by Paul Beckingham
parent cba5948a1d
commit a8bab90c34

View file

@ -282,9 +282,8 @@ and project. The others are sent to standard output.
.TP .TP
.B confirmation=yes .B confirmation=yes
May be "yes" or "no", and determines whether taskwarrior will ask for May be "yes" or "no", and determines whether taskwarrior will ask for
confirmation before deleting a task, performing bulk changes, or the undo confirmation before deleting a task or performing the undo command. The default
command. The default value is "yes". Consider leaving this setting as "yes", value is "yes". Consider leaving this setting as "yes", for safety.
for safety.
.TP .TP
.B allow.empty.filter=yes .B allow.empty.filter=yes
@ -313,9 +312,9 @@ Controls padding between columns of the report output. Default is "1".
.TP .TP
.B bulk=3 .B bulk=3
Is a number, defaulting to 3. When this number or greater of tasks are modified Is a number, defaulting to 3. When this number or greater of tasks are modified
in a single command, confirmation will be required, unless the in a single command, confirmation will be required, regardless of the value of
.B confirmation .B confirmation
variable is "no". variable.
This is useful for preventing large-scale unintended changes. This is useful for preventing large-scale unintended changes.