mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-28 22:03:12 +00:00
8d7416048d
This checked specifically for "| and" and "a=b" and then just gave the
error without a caret at all.
E.g. for a /tmp/broken.fish that contains
```fish
echo foo
echo foo | and cat
```
This would print:
```
/tmp/broken.fish (line 3): The 'and' command can not be used in a pipeline
warning: Error while reading file /tmp/broken.fish
```
without any indication other than the line number as to the location
of the error.
Now we do
```
/tmp/broken.fish (line 3): The 'and' command can not be used in a pipeline
echo foo | and cat
^~^
warning: Error while reading file /tmp/broken.fish
```
Another nice one:
```
fish --no-config -c 'echo notprinted; echo foo; a=b'
```
failed to give the error message!
(Note: Is it really a "warning" if we failed to read the one file we
wer told to?)
We should check if we should either centralize these error messages
completely, or always pass them and remove this "code" system, because
it's only used in some cases.
103 lines
1.7 KiB
Fish
103 lines
1.7 KiB
Fish
# RUN: %fish %s
|
|
|
|
# erase all lowercase variables to make sure they don't break our tests
|
|
for varname in (set -xn | string match -r '^[a-z].*')
|
|
while set -q $varname
|
|
set -e $varname
|
|
end
|
|
end
|
|
|
|
# CHECK: bar
|
|
foo=bar echo $foo
|
|
|
|
# CHECK: nil
|
|
set -q foo; or echo nil
|
|
|
|
# CHECK: lx
|
|
foo=bar set -qlx foo; and echo lx
|
|
|
|
# CHECK: 3
|
|
a={1, 2, 3} count $a
|
|
|
|
# CHECK: 1+2+3
|
|
a={1, 2, 3} string join + $a
|
|
|
|
# CHECK: 1 2 3
|
|
a=(echo 1 2 3) echo $a
|
|
|
|
# CHECK: a a2
|
|
a=a b={$a}2 echo $a $b
|
|
|
|
# CHECK: a
|
|
a=a builtin echo $a
|
|
|
|
# CHECK: 0
|
|
a=failing-glob-* count $a
|
|
|
|
# CHECK: ''
|
|
a=b true | echo "'$a'"
|
|
|
|
if a=b true
|
|
# CHECK: ''
|
|
echo "'$a'"
|
|
end
|
|
|
|
# CHECK: b
|
|
not a=b echo $a
|
|
|
|
# CHECK: b
|
|
a=b not echo $a
|
|
|
|
# CHECK: b
|
|
a=b not builtin echo $a
|
|
|
|
# CHECK: /usr/bin:/bin
|
|
xPATH={/usr,}/bin sh -c 'echo $xPATH'
|
|
|
|
# CHECK: 2
|
|
yPATH=/usr/bin:/bin count $yPATH
|
|
|
|
# CHECK: b
|
|
a=b begin
|
|
true | echo $a
|
|
end
|
|
|
|
# CHECK: b
|
|
a=b if true
|
|
echo $a
|
|
end
|
|
|
|
# CHECK: b
|
|
a=b switch x
|
|
case x
|
|
echo $a
|
|
end
|
|
|
|
complete -c x --erase
|
|
complete -c x -xa arg
|
|
complete -C' a=b x ' # Mind the leading space.
|
|
# CHECK: arg
|
|
alias xalias=x
|
|
complete -C'a=b xalias '
|
|
# CHECK: arg
|
|
alias envxalias='a=b x'
|
|
complete -C'a=b envxalias '
|
|
# CHECK: arg
|
|
|
|
# Eval invalid grammar to allow fish to parse this file
|
|
eval 'a=(echo b)'
|
|
# CHECKERR: {{.*}}: Unsupported use of '='. In fish, please use 'set a (echo b)'.
|
|
# CHECKERR: a=(echo b)
|
|
# CHECKERR: ^~~~~~~~~^
|
|
eval ': | a=b'
|
|
# CHECKERR: {{.*}}: Unsupported use of '='. In fish, please use 'set a b'.
|
|
# CHECKERR: : | a=b
|
|
# CHECKERR: ^~^
|
|
eval 'not a=b'
|
|
# CHECKERR: {{.*}}: Unsupported use of '='. In fish, please use 'set a b'.
|
|
# CHECKERR: not a=b
|
|
# CHECKERR: ^~^
|
|
|
|
complete -c foo -xa '$a'
|
|
a=b complete -C'foo '
|
|
#CHECK: b
|