tests/checks/empty.fish

# RUN: %fish %s

# See issue 5692

function empty
end

# functions should not preserve $status
false
empty
echo $status
# CHECK: 0
true
empty
echo $status
# CHECK: 0

# blocks should preserve $status
false
begin
end
echo $status
# CHECK: 1
true
begin
end
echo $status
# CHECK: 0
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 12:19:32 +02:00			`# RUN: %fish %s`
Port empty functions test to littlecheck 2019-12-07 11:02:22 -08:00
			`# See issue 5692`

			`function empty`
			`end`

			`# functions should not preserve $status`
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-13 20:34:22 +01:00			`false`
			`empty`
			`echo $status`
Port empty functions test to littlecheck 2019-12-07 11:02:22 -08:00			`# CHECK: 0`
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-13 20:34:22 +01:00			`true`
			`empty`
			`echo $status`
Port empty functions test to littlecheck 2019-12-07 11:02:22 -08:00			`# CHECK: 0`

			`# blocks should preserve $status`
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-13 20:34:22 +01:00			`false`
			`begin`
			`end`
			`echo $status`
Port empty functions test to littlecheck 2019-12-07 11:02:22 -08:00			`# CHECK: 1`
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-13 20:34:22 +01:00			`true`
			`begin`
			`end`
			`echo $status`
Port empty functions test to littlecheck 2019-12-07 11:02:22 -08:00			`# CHECK: 0`