| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
|
| |
As far as I know we can't access the build artifacts from Travis, so we
can't check the interactive logs after a test failure. Add an
environment variable that causes the test runner to dump the logs
itself, and set that variable for Travis.
|
|
|
|
|
|
|
| |
Also avoid resetting bindings if fish_key_bindings is "modified" without
actually changing.
Fixes #1638.
|
|
|
|
|
|
|
| |
This was apparently what was interfering with the tests working on
Linux.
Tweak .travis.yml to install expect so the tests run on Linux.
|
|
|
|
|
|
|
| |
Add a test harness that uses `expect` to drive Fish to test interactive
behavior.
Include some tests for `read`.
|
|
|
|
|
|
|
|
|
| |
Split `make test` into two targets `make test_low_level` and `make
test_fishscript`, primarily so fishscript tests can be rechecked quickly
after edits.
Reformat the test.fish file and update some of the code to be a little
more straightforward (e.g. `if not cmd` instead of `if cmd; else`).
|
|
|
|
|
| |
Usage: read -n nchars
Reads maximum of nchars characters. If nchars <= 0, there's no limit.
|
|
|
|
|
| |
GNU sort behaves stupidly when LC_ALL is not C. This caused the test
output to be sorted wrong.
|
| |
|
|
|
|
|
|
|
| |
When $IFS is empty, command substitution no longer splits on newlines.
However we still want to trim off a single trailing newline, as most
commands will emit a trailing newline and it makes it harder to work
with their output.
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|