github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-11-24 09:46:47 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
cf8219e3ce
fish-shell/tests/checks/invocation.fish

59 lines
1.9 KiB
Fish
Raw Normal View History

set error code on failed command substitution to 255 instead of -1 the exit status ought to be in 0-255, e.g. exit -1
2020-01-17 22:08:14 +08:00
#RUN: %fish -C 'set -l fish %fish' %s
$fish -c "echo 1.2.3.4."
Port most of the invocation tests to littlecheck This is a bit weird sometimes, e.g. to test the return status (that fish actually *returns $status*), we use a #RUN line with %fish invoking %fish, so we can use the substitution. Still much nicer. The missing scripts are those that rely on config.
2019-06-26 02:47:28 +08:00
# CHECK: 1.2.3.4.
set error code on failed command substitution to 255 instead of -1 the exit status ought to be in 0-255, e.g. exit -1
2020-01-17 22:08:14 +08:00
Rationalize $status and errors Prior to this fix, fish was rather inconsistent in when $status gets set in response to an error. For example, a failed expansion like "$foo[" would not modify $status. This makes the following inter-related changes: 1. String expansion now directly returns the value to set for $status on error. The value is always used. 2. parser_t::eval() now directly returns the proc_status_t, which cleans up a lot of call sites. 3. We expose a new function exec_subshell_for_expand() which ignores $status but returns errors specifically related to subshell expansion. 4. We reify the notion of "expansion breaking" errors. These include command-not-found, expand syntax errors, and others. The upshot is we are more consistent about always setting $status on errors.
2020-01-24 09:34:46 +08:00
PATH= $fish -c "command a" 2>/dev/null
echo $status
# CHECK: 127
set error code on failed command substitution to 255 instead of -1 the exit status ought to be in 0-255, e.g. exit -1
2020-01-17 22:08:14 +08:00
PATH= $fish -c "echo (command a)" 2>/dev/null
echo $status
Rationalize $status and errors Prior to this fix, fish was rather inconsistent in when $status gets set in response to an error. For example, a failed expansion like "$foo[" would not modify $status. This makes the following inter-related changes: 1. String expansion now directly returns the value to set for $status on error. The value is always used. 2. parser_t::eval() now directly returns the proc_status_t, which cleans up a lot of call sites. 3. We expose a new function exec_subshell_for_expand() which ignores $status but returns errors specifically related to subshell expansion. 4. We reify the notion of "expansion breaking" errors. These include command-not-found, expand syntax errors, and others. The upshot is we are more consistent about always setting $status on errors.
2020-01-24 09:34:46 +08:00
# CHECK: 127
Move the invocation checks to invocation.fish These where separate files so we could use the %s substitution to run that fish, but since discovering setting $fish that workaround isn't necessary.
2020-04-01 01:52:56 +08:00
if not set -q GITHUB_WORKFLOW
$fish -c 'if status --is-login ; echo login shell ; else ; echo not login shell ; end; if status --is-interactive ; echo interactive ; else ; echo not interactive ; end' -i
# CHECK: not login shell
# CHECK: interactive
$fish -c 'if status --is-login ; echo login shell ; else ; echo not login shell ; end; if status --is-interactive ; echo interactive ; else ; echo not interactive ; end' -l -i
# CHECK: login shell
# CHECK: interactive
else
Fix typo
2020-10-31 09:23:28 +08:00
# GitHub Action doesn't start this in a terminal, so fish would complain.
Move the invocation checks to invocation.fish These where separate files so we could use the %s substitution to run that fish, but since discovering setting $fish that workaround isn't necessary.
2020-04-01 01:52:56 +08:00
# Instead, we just fake the result, since we have no way to indicate a skipped test.
echo not login shell
echo interactive
echo login shell
echo interactive
end
$fish -c 'if status --is-login ; echo login shell ; else ; echo not login shell ; end; if status --is-interactive ; echo interactive ; else ; echo not interactive ; end' -l
# CHECK: login shell
# CHECK: not interactive
$fish -c 'if status --is-login ; echo login shell ; else ; echo not login shell ; end; if status --is-interactive ; echo interactive ; else ; echo not interactive ; end'
# CHECK: not login shell
# CHECK: not interactive
$fish -c 'if status --is-login ; echo login shell ; else ; echo not login shell ; end; if status --is-interactive ; echo interactive ; else ; echo not interactive ; end' -l
# CHECK: login shell
# CHECK: not interactive
Read arguments with `fish -c` This reads any additional positional arguments given to `fish -c` into $argv. We don't handle the first argument specially (as `$0`) as that's confusing and doesn't seem very useful. Fixes #2314.
2020-09-26 20:45:51 +08:00
Add more tests for -c arguments
2020-09-26 21:05:26 +08:00
# Arguments for -c
Read arguments with `fish -c` This reads any additional positional arguments given to `fish -c` into $argv. We don't handle the first argument specially (as `$0`) as that's confusing and doesn't seem very useful. Fixes #2314.
2020-09-26 20:45:51 +08:00
$fish -c 'string escape $argv' 1 2 3
# CHECK: 1
# CHECK: 2
# CHECK: 3
Add more tests for -c arguments
2020-09-26 21:05:26 +08:00
# Two -cs
$fish -c 'string escape y$argv' -c 'string escape x$argv' 1 2 3
# CHECK: y1
# CHECK: y2
# CHECK: y3
# CHECK: x1
# CHECK: x2
# CHECK: x3
Exit if --no-execute is enabled don't interactively read from the terminal Don't go into implicit interactive mode without ever executing anything - not even `exit` or reacting to ctrl-d. That just renders the shell useless and unquittable.
2021-01-02 04:15:09 +08:00
# Should just do nothing.
$fish --no-execute
Reference in New Issue Copy Permalink