Make tests usable with path with spaces
This is somewhat subtle:
The #RUN line in a littlecheck file will be run by a posix shell,
which means the substitutions will also be mangled by it.
Now, we *have* shell-quoted them, but unfortunately what we need is to
quote them for inside a pre-existing layer of quotes, e.g.
# RUN: fish -C 'set -g fish %fish'
here, %fish can't be replaced with `'path with spaces/fish'`, because
that ends up as
# RUN: fish -C 'set -g fish 'path with spaces/fish''
which is just broken.
So instead, we pass it as a variable to that fish:
# RUN: fish=%fish fish...
In addition, we need to not mangle the arguments in our test_driver.
For that, because we insist on posix shell, which has only one array,
and we source a file, we *need* to stop having that file use
arguments.
Which is okay - test_env.sh could previously be used to start a test,
and now it no longer can because that is test_*driver*.sh's job.
For the interactive tests, it's slightly different:
pexpect.spawn(foo) is sensitive to shell metacharacters like space.
So we shell-quote it.
But if you pass any args to pexpect.spawn, it no longer uses a shell,
and so we cannot shell-quote it.
There could be a better way to fix this?
2024-12-27 19:54:43 +00:00
|
|
|
#RUN: fish=%fish %fish %s
|
2020-02-07 21:10:55 +00:00
|
|
|
# Test that using variables as command names work correctly.
|
|
|
|
|
|
|
|
$EMPTY_VARIABLE
|
|
|
|
#CHECKERR: {{.*}}checks/vars_as_commands.fish (line {{\d+}}): The expanded command was empty.
|
|
|
|
#CHECKERR: $EMPTY_VARIABLE
|
2022-08-11 16:20:40 +00:00
|
|
|
#CHECKERR: ^~~~~~~~~~~~~~^
|
2020-02-07 21:10:55 +00:00
|
|
|
"$EMPTY_VARIABLE"
|
|
|
|
#CHECKERR: {{.*}}checks/vars_as_commands.fish (line {{\d+}}): The expanded command was empty.
|
|
|
|
#CHECKERR: "$EMPTY_VARIABLE"
|
2022-08-11 16:20:40 +00:00
|
|
|
#CHECKERR: ^~~~~~~~~~~~~~~~^
|
2020-02-07 21:10:55 +00:00
|
|
|
|
|
|
|
set CMD1 echo basic command as variable
|
|
|
|
$CMD1
|
|
|
|
#CHECK: basic command as variable
|
|
|
|
|
|
|
|
set CMD2 echo '(' not expanded again
|
|
|
|
$CMD2
|
|
|
|
#CHECK: ( not expanded again
|
|
|
|
|
|
|
|
# Test using variables with the builtin decorator
|
|
|
|
builtin $CMD1
|
|
|
|
#CHECK: basic command as variable
|
|
|
|
|
|
|
|
# Test implicit cd
|
|
|
|
set CMD3 /usr/bin
|
|
|
|
$CMD3 && echo $PWD
|
|
|
|
#CHECK: /usr/bin
|
|
|
|
|
2021-07-26 19:29:02 +00:00
|
|
|
# $status specifically is not valid, to avoid a common error
|
|
|
|
# with `if $status`
|
|
|
|
echo 'if $status; echo foo; end' | $fish --no-config
|
|
|
|
#CHECKERR: fish: $status is not valid as a command. See `help conditions`
|
|
|
|
#CHECKERR: if $status; echo foo; end
|
2022-08-12 14:53:31 +00:00
|
|
|
#CHECKERR: ^~~~~~^
|
2021-07-26 19:29:02 +00:00
|
|
|
echo 'not $status' | $fish --no-config
|
|
|
|
#CHECKERR: fish: $status is not valid as a command. See `help conditions`
|
|
|
|
#CHECKERR: not $status
|
2022-08-12 14:53:31 +00:00
|
|
|
#CHECKERR: ^~~~~~^
|
2021-07-26 19:29:02 +00:00
|
|
|
|
|
|
|
# Script doesn't run at all.
|
|
|
|
echo 'echo foo; and $status' | $fish --no-config
|
|
|
|
#CHECKERR: fish: $status is not valid as a command. See `help conditions`
|
|
|
|
#CHECKERR: echo foo; and $status
|
2022-08-12 14:53:31 +00:00
|
|
|
#CHECKERR: ^~~~~~^
|
2021-07-26 19:29:02 +00:00
|
|
|
|
|
|
|
echo 'set -l status_cmd true; if $status_cmd; echo Heck yes this is true; end' | $fish --no-config
|
|
|
|
#CHECK: Heck yes this is true
|
|
|
|
|
2022-08-11 15:31:01 +00:00
|
|
|
foo=bar $NONEXISTENT -c 'set foo 1 2 3; set --show foo'
|
|
|
|
#CHECKERR: {{.*}}checks/vars_as_commands.fish (line {{\d+}}): The expanded command was empty.
|
|
|
|
#CHECKERR: foo=bar $NONEXISTENT -c 'set foo 1 2 3; set --show foo'
|
|
|
|
#CHECKERR: ^~~~~~~~~~~^
|
|
|
|
|
2020-02-07 21:10:55 +00:00
|
|
|
exit 0
|