Mirrors/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell synced 2025-01-16 06:54:03 +00:00
Code Issues Projects Releases Packages Wiki Activity
fish-shell/tests/checks/no-execute.fish

37 lines
888 B
Fish
Raw Normal View History

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
Silence some errors for `fish --no-execute` It used to error out when a command wasn't known, even when it was a function that would only be discovered via autoloading. Now we just accept that a command doesn't exist when no-execute is given - we're not gonna execute it anyway. Also, in the same breath stop counting empty commands after expansion and empty wildcard expansions as errors - these depend on runtime values, so we can't verify them without executing. Fixes #977. (note that it still executes "time", but that's another commit)
2020-02-17 10:12:01 +00:00
# Test that fish -n doesn't check for command existence - function autoloading throws a wrench in that.
echo "type foo" | $fish -n
echo $status
#CHECK: 0
Don't time --no-execute This made some output for non-execution. See #977.
2020-02-17 10:38:21 +00:00
# Test that it doesn't time non-execution.
echo "time echo foo" | $fish -n
echo $status
#CHECK: 0
Silence some errors for `fish --no-execute` It used to error out when a command wasn't known, even when it was a function that would only be discovered via autoloading. Now we just accept that a command doesn't exist when no-execute is given - we're not gonna execute it anyway. Also, in the same breath stop counting empty commands after expansion and empty wildcard expansions as errors - these depend on runtime values, so we can't verify them without executing. Fixes #977. (note that it still executes "time", but that's another commit)
2020-02-17 10:12:01 +00:00
# Test that it doesn't check globs.
echo "echo /asfjidhfiusnlkxcnvklxcvlkmcxlv*" | $fish -n
echo $status
#CHECK: 0
# Test that it does print syntax errors.
echo "begin; echo oops" | $fish -n
#CHECKERR: fish: Missing end to balance this begin
#CHECKERR: begin; echo oops
Add acceptable errors to tests
2022-08-11 15:22:03 +00:00
#CHECKERR: ^~~~^
Silence some errors for `fish --no-execute` It used to error out when a command wasn't known, even when it was a function that would only be discovered via autoloading. Now we just accept that a command doesn't exist when no-execute is given - we're not gonna execute it anyway. Also, in the same breath stop counting empty commands after expansion and empty wildcard expansions as errors - these depend on runtime values, so we can't verify them without executing. Fixes #977. (note that it still executes "time", but that's another commit)
2020-02-17 10:12:01 +00:00
echo $status
#CHECK: 127
Don't replace tilde for error messages if we have no $HOME This was an issue with "--no-execute", which has no variables and therefore no $HOME: ```fish fish --no-execute /path/to/file ``` would say the error is in `~/path/to/file`. Instead, since this is just for a message, we simply return the filename without doing the replacement. Fixes #10171
2023-12-28 09:18:00 +00:00
echo "begin" > broken
$fish -n $PWD/broken
#CHECKERR: /{{.*}}broken (line 1): Missing end to balance this begin
#CHECKERR: begin
#CHECKERR: ^~~~^
#CHECKERR: warning: Error while reading file /{{.*}}broken
rm broken
Silence some errors for `fish --no-execute` It used to error out when a command wasn't known, even when it was a function that would only be discovered via autoloading. Now we just accept that a command doesn't exist when no-execute is given - we're not gonna execute it anyway. Also, in the same breath stop counting empty commands after expansion and empty wildcard expansions as errors - these depend on runtime values, so we can't verify them without executing. Fixes #977. (note that it still executes "time", but that's another commit)
2020-02-17 10:12:01 +00:00
# Littlecheck assumes a status of 127 means the shebang was invalid.
exit 0
Reference in a new issue Copy permalink