Bug ID 24984
Summary auto-confirm setting produces unexpected results
Component All Bugs
Normally, the command "process handle -n false" produces an "do you want to change ALL signals" prompt. When auto-confirm is true, this command essentially becomes a no-op, since the confirmation logic automatically responds "no". The description of this setting is "If true all confirmation prompts will receive their default reply.", so it essence this is working as intended, but i think it produces very surprising results (e.g. the above command is silently ignored). I think it would be better to have this setting mean "just shut up and do it", i.e., perform all actions without asking the usual "are you sure" questions.