ridiculousfish 38f4330683 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-25 17:28:41 -08:00
..
2019-12-01 18:14:26 +01:00
2019-06-26 21:19:40 +02:00
2020-01-25 12:59:18 -08:00
2019-06-26 21:19:40 +02:00
2020-01-25 17:28:41 -08:00
2020-01-25 17:28:41 -08:00
2019-11-26 18:12:24 +01:00
2019-07-09 10:02:50 -07:00
2020-01-18 10:43:59 +01:00
2019-11-25 13:07:15 +01:00