| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
Due to being read-only, SHLVL wasn't being incremented properly for
recursive invocations of fish.
|
|\
| |
| | |
Fix various expansions issues with variables
|
|\ \
| | |
| | |
| | | |
kballard-make_type_better
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The span now properly points at the token that was invalid, rather than
the start of the slice.
Also fix the span for `()[1]` and `()[d]`, which were previously
reporting no source location at all.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a variable is parsed as being empty, parse out the slice and
validate the indexes anyway, behaving for slicing purposes as if the
variable had a single empty value.
Besides providing errors when expected, this also fixes the following:
set -l foo
echo "$foo[1]"
This used to print "[1]", now it properly prints nothing.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Double expansions of variables had the following issues:
* `"$$foo"` threw an error no matter what the value of `$foo` was.
* `set -l foo ''; echo $$foo` threw an error because of the expansion of
`$foo` to `''`.
With this change, double expansion always works properly. When
double-expanding a multi-valued variable, in a double-quoted string the
first word of the inner expansion is used for the outer expansion, and
outside of a quoted string every word is used for the double-expansion
in each of the arguments.
> set -l foo bar baz
> set -l bar one two
> set -l baz three four
> echo "$$foo"
one two baz
> echo $$foo
one two three four
|
| |
| |
| |
| | |
Fixes #1581
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Enhance the `read` builtin to support creating an array with the --array
flag. With --array, only a single variable name is allowed and the
entire input is tokenized and placed into that variable as an array.
Also add custom behavior if IFS is empty or unset. In that event, split
the input on every character, instead of the previous behavior of doing
no splitting at all.
|
|/
|
|
|
|
| |
One of the tests was using `>/dev/null` to suppress the `type` output.
That needs to be `^/dev/null` now, but instead just go ahead and use the
new `-q` flag.
|
|
|
|
| |
Fixes #1543
|
|
|
|
| |
used accidentally
|
| |
|
|
|
|
| |
Fixes #1459
|
| |
|
| |
|
|
|
|
| |
with the job, fixing psub. Fixes #1394
|
| |
|
|
|
|
| |
test for it too.
|
|
|
|
| |
#1297.
|
|
|
|
| |
shells. Fixes #1061.
|
| |
|
| |
|
| |
|
|
|
|
| |
pass (!). Error reporting still unsteady.
|
| |
|
| |
|
|
|
|
| |
https://github.com/fish-shell/fish-shell/issues/110
|
|
|
|
| |
stderr may be output twice.
|
| |
|
| |
|
|
|
|
|
|
| |
finally pass.
https://github.com/fish-shell/fish-shell/issues/624
|
|
|
|
| |
Is git breaking line endings?
|
| |
|
| |
|
|
|
|
|
|
|
| |
unless it fails
https://github.com/fish-shell/fish-shell/issues/547
https://github.com/fish-shell/fish-shell/issues/214
|
| |
|
|
|
|
| |
https://github.com/fish-shell/fish-shell/issues/137
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Addresses issue described in https://github.com/fish-shell/fish-shell/issues/347#issuecomment-10650443
|
|
|
|
|
|
|
| |
essentially delete the newline, within normal text or double quotes. Backslashes are retained within single quotes.
Fixes https://github.com/fish-shell/fish-shell/issues/347
Fixes https://github.com/fish-shell/fish-shell/issues/52
|
|
|
|
| |
https://github.com/fish-shell/fish-shell/issues/399
|
|
|
|
| |
https://github.com/fish-shell/fish-shell/issues/359
|
| |
|
|
|
|
|
|
| |
interpret them
https://github.com/fish-shell/fish-shell/issues/337
|
|
|
|
|
|
|
| |
implements short-circuiting for and/or so that non-existent commands don't produce error messages.
Fixes https://github.com/fish-shell/fish-shell/issues/345
Fixes https://github.com/fish-shell/fish-shell/issues/349
|
| |
|
| |
|