fish-shell/tests/test_cmdsub.err


####################
# Command sub just under the limit should succeed

####################
# Command sub at the limit should fail
fish: Too much data emitted by command substitution so it was discarded

set b (string repeat -n 512 x)
      ^

####################
# Command sub over the limit should fail
fish: Too much data emitted by command substitution so it was discarded

    set -l x (string repeat -n $argv x)
             ^
in function 'subme' with arguments '513'
in command substitution

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

####################
# Same builtin in a command substitution is affected
fish: Too much data emitted by command substitution so it was discarded

echo this will fail (string repeat --max 513 b) to output anything
                    ^
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-04 04:25:20 +00:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-04 03:56:14 +00:00			`# Command sub just under the limit should succeed`
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-04 04:25:20 +00:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-04 03:56:14 +00:00			`# Command sub at the limit should fail`
Revert "Update tests" This reverts commit 36367e4882a7278b347a5b8d1d55b67c3ecddc59. 2018-11-28 14:27:21 +00:00			`fish: Too much data emitted by command substitution so it was discarded`
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-27 03:17:04 +00:00
			`set b (string repeat -n 512 x)`
			`^`
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-04 04:25:20 +00:00
			`####################`
use new `logmsg` and `set --show` in tests 2017-08-04 03:56:14 +00:00			`# Command sub over the limit should fail`
Revert "Update tests" This reverts commit 36367e4882a7278b347a5b8d1d55b67c3ecddc59. 2018-11-28 14:27:21 +00:00			`fish: Too much data emitted by command substitution so it was discarded`
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-27 03:17:04 +00:00
Stop copying out function definition when executing a function This switches function execution from the function's source code to its stored node and pstree. This means we no longer have to re-parse the function every time we execute it. 2018-02-12 03:34:12 +00:00			`set -l x (string repeat -n $argv x)`
			`^`
Remove "called on standard input" message This was printed basically everywhere. The user knows what they executed on standard input. A good example: ```fish set c (subme 513) ``` used to print ``` fish: Too much data emitted by command substitution so it was discarded set -l x (string repeat -n $argv x) ^ in function 'subme' called on standard input with parameter list '513' in command substitution called on standard input ``` and now it is ``` fish: Too much data emitted by command substitution so it was discarded set -l x (string repeat -n $argv x) ^ in function 'subme' with arguments '513' in command substitution ``` See #5434. 2019-03-26 16:10:56 +00:00			`in function 'subme' with arguments '513'`
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-27 03:17:04 +00:00			`in command substitution`

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-04 04:25:20 +00:00			`####################`
use new `logmsg` and `set --show` in tests 2017-08-04 03:56:14 +00:00			`# Make sure output from builtins outside of command substitution is not 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-04 04:25:20 +00: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-27 03:17:04 +00:00			`# Same builtin in a command substitution is affected`
Revert "Update tests" This reverts commit 36367e4882a7278b347a5b8d1d55b67c3ecddc59. 2018-11-28 14:27:21 +00:00			`fish: Too much data emitted by command substitution so it was discarded`
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-27 03:17:04 +00:00
			`echo this will fail (string repeat --max 513 b) to output anything`
			`^`