fish/tests/test_cmdsub.out


####################
# Command sub just under the limit should succeed
$a: not set in local scope
$a: set in global scope, unexported, with 1 elements
$a[1]: length=511 value=|xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx|
$a: not set in universal scope


####################
# Command sub at the limit should fail
$b: not set in local scope
$b: not set in global scope
$b: not set in universal scope


####################
# Command sub over the limit should fail
$c: not set in local scope
$c: set in global scope, unexported, with 1 elements
$c[1]: length=0 value=||
$c: not set in universal scope


####################
# Make sure output from builtins outside of command substitution is not affected
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

####################
# Same builtin in a command substitution is affected
use new `logmsg` and `set --show` in tests Also modify `logmsg` to output additional separator lines to make the demarcation between tests even clearer. 2017-08-03 21:25:20 -07:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-03 20:56:14 -07:00			`# Command sub just under the limit should succeed`
			`$a: not set in local scope`
			`$a: set in global scope, unexported, with 1 elements`
fix `set --show` output I realized I was printing individual var entries using zero based indexing (like C++) when the indexes should be one based. 2017-08-04 17:08:25 -07:00			$a[1]: length=511 value=\|xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\|
use new `logmsg` and `set --show` in tests 2017-08-03 20:56:14 -07:00			`$a: not set in universal scope`

use new `logmsg` and `set --show` in tests Also modify `logmsg` to output additional separator lines to make the demarcation between tests even clearer. 2017-08-03 21:25:20 -07:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-03 20:56:14 -07:00			`# Command sub at the limit should fail`
			`$b: not set in local scope`
			`$b: not set in global scope`
			`$b: not set in universal scope`

use new `logmsg` and `set --show` in tests Also modify `logmsg` to output additional separator lines to make the demarcation between tests even clearer. 2017-08-03 21:25:20 -07:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-03 20:56:14 -07:00			`# Command sub over the limit should fail`
			`$c: not set in local scope`
fix `set --show` of semi-empty var A semi-empty var is one with a single empty string element. The `env_var_t::empty()` method returns true for such vars but we want `set --show` to report that it has a single empty element. 2017-08-16 13:39:48 -07:00			`$c: set in global scope, unexported, with 1 elements`
			`$c[1]: length=0 value=\|\|`
use new `logmsg` and `set --show` in tests 2017-08-03 20:56:14 -07:00			`$c: not set in universal scope`

use new `logmsg` and `set --show` in tests Also modify `logmsg` to output additional separator lines to make the demarcation between tests even clearer. 2017-08-03 21:25:20 -07:00
			`####################`
implement limits on command substitution output This makes command substitutions impose the same limit on the amount of data they accept as the `read` builtin. It does not limit output of external commands or builtins in other contexts. Fixes #3822 2017-07-26 20:17:04 -07:00			`# Make sure output from builtins outside of command substitution is not affected`
			aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
use new `logmsg` and `set --show` in tests Also modify `logmsg` to output additional separator lines to make the demarcation between tests even clearer. 2017-08-03 21:25:20 -07:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-03 20:56:14 -07:00			`# Same builtin in a command substitution is affected`