fish-shell/tests/checks/exit-status-with-closing-stderr.fish

# RUN: %fish %s
argparse r-require= -- --require 2>/dev/null
echo $status
# CHECK: 2
argparse r-require= -- --require 2>&-
echo $status
# CHECK: 2
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 18:19:32 +08:00			`# RUN: %fish %s`
Run fish_indent on all our fish scripts It's now good enough to do so. We don't allow grid-alignment: ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` becomes ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` It's just more trouble than it is worth. The one part I'd change: We align and/or'd parts of an if-condition with the in-block code: ```fish if true and false dosomething end ``` becomes ```fish if true and false dosomething end ``` but it's not used terribly much and if we ever fix it we can just reindent. 2020-01-14 03:34:22 +08:00			`argparse r-require= -- --require 2>/dev/null`
			`echo $status`
Don't override exit status when stderr is closed by `2>&-` fixes #6470 2020-01-07 20:48:57 +08:00			`# CHECK: 2`
Run fish_indent on all our fish scripts It's now good enough to do so. We don't allow grid-alignment: ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` becomes ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` It's just more trouble than it is worth. The one part I'd change: We align and/or'd parts of an if-condition with the in-block code: ```fish if true and false dosomething end ``` becomes ```fish if true and false dosomething end ``` but it's not used terribly much and if we ever fix it we can just reindent. 2020-01-14 03:34:22 +08:00			`argparse r-require= -- --require 2>&-`
			`echo $status`
Don't override exit status when stderr is closed by `2>&-` fixes #6470 2020-01-07 20:48:57 +08:00			`# CHECK: 2`