From a8bab90c347ec3485f3e017cc494d010124c396b Mon Sep 17 00:00:00 2001 From: Tomas Babej Date: Thu, 22 Jan 2015 09:11:02 +0100 Subject: [PATCH] Documentation - Update the man page with the correct description of behaviour of rc.confirmation and rc.bulk variables --- doc/man/taskrc.5.in | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/man/taskrc.5.in b/doc/man/taskrc.5.in index a728cb49a..a43998ca0 100644 --- a/doc/man/taskrc.5.in +++ b/doc/man/taskrc.5.in @@ -282,9 +282,8 @@ and project. The others are sent to standard output. .TP .B confirmation=yes May be "yes" or "no", and determines whether taskwarrior will ask for -confirmation before deleting a task, performing bulk changes, or the undo -command. The default value is "yes". Consider leaving this setting as "yes", -for safety. +confirmation before deleting a task or performing the undo command. The default +value is "yes". Consider leaving this setting as "yes", for safety. .TP .B allow.empty.filter=yes @@ -313,9 +312,9 @@ Controls padding between columns of the report output. Default is "1". .TP .B bulk=3 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 -variable is "no". +variable. This is useful for preventing large-scale unintended changes.