fish-shell/tests/test1.err


####################
# Comments in odd places don't cause problems

####################
# Bracket expansion

####################
# Escaped newlines

####################
# Simple function tests

####################
# Testing builtin status

####################
# Verify that we can turn stderr into stdout and then pipe it

####################
# Test that trailing ^ doesn't trigger redirection, see #1873

####################
# Verify that we can pipe something other than stdout

####################
# echo tests

####################
# Verify that pipes don't conflict with fd redirections

####################
# Make sure while loops don't run forever with no-exec (#1543)

####################
# For loops with read-only vars is an error (#4342)
fish: You cannot use read-only variable 'status' in a for loop
for status in a b c
    ^

####################
# That goes for non-electric ones as well (#5548)
fish: You cannot use read-only variable 'hostname' in a for loop
for hostname in a b c
    ^

####################
# For loop control vars available outside the for block

####################
# Comments allowed in between lines (#1987)

####################
# Backslashes are part of comments and do not join lines (#1255)

####################
# Verify $argv set correctly in sourced scripts (#139)
use new `logmsg` and `set --show` in tests 2017-08-05 04:33:47 +08:00
			`####################`
			`# Comments in odd places don't cause problems`

			`####################`
			`# Bracket expansion`

			`####################`
			`# Escaped newlines`

			`####################`
			`# Simple function tests`

			`####################`
Fix tests expecting non-zero status after empty function call 2019-04-14 01:04:44 +08:00			`# Testing builtin status`
use new `logmsg` and `set --show` in tests 2017-08-05 04:33:47 +08:00
			`####################`
			`# Verify that we can turn stderr into stdout and then pipe it`

			`####################`
			`# Test that trailing ^ doesn't trigger redirection, see #1873`

			`####################`
			`# Verify that we can pipe something other than stdout`

			`####################`
			`# echo tests`

			`####################`
			`# Verify that pipes don't conflict with fd redirections`

			`####################`
			`# Make sure while loops don't run forever with no-exec (#1543)`

Report error when using read-only var in for loop Using a read-only variable like `status` as a for loop control variable has never worked. But without this change you simply get non-sensical behavior that leaves you scratching your head in puzzlement. This change replaces the non-sensical behavior with an explicit error message. Fixes #4342 2017-08-21 03:02:45 +08:00			`####################`
			`# For loops with read-only vars is an error (#4342)`
Revert "Update tests" This reverts commit 36367e4882a7278b347a5b8d1d55b67c3ecddc59. 2018-11-28 22:27:21 +08:00			`fish: You cannot use read-only variable 'status' in a for loop`
Report error when using read-only var in for loop Using a read-only variable like `status` as a for loop control variable has never worked. But without this change you simply get non-sensical behavior that leaves you scratching your head in puzzlement. This change replaces the non-sensical behavior with an explicit error message. Fixes #4342 2017-08-21 03:02:45 +08:00			`for status in a b c`
			`^`

Also set the read-only flag for non-electric vars For some reason, we have two places where a variable can be read-only: - By key in env.cpp:is_read_only(), which is checked via set* - By flag on the actual env_var_t, which is checked e.g. in parse_execution The latter didn't happen for non-electric variables like hostname, because they used the default constructor, because they were constructed via operator[] (or some such C++-iness). This caused for-loops to crash on an assert if they used a non-electric read-only var like $hostname or $SHLVL. Instead, we explicitly set the flag. We might want to remove one of the two read-only checks, or something? Fixes #5548. 2019-01-19 02:24:49 +08:00			`####################`
			`# That goes for non-electric ones as well (#5548)`
			`fish: You cannot use read-only variable 'hostname' in a for loop`
			`for hostname in a b c`
			`^`

Hoist `for` loop control var to enclosing scope (#4376) * Hoist `for` loop control var to enclosing scope It should be possible to reference the last value assigned to a `for` loop control var when the loop terminates. This makes it easier to detect if we broke out of the loop among other things. This change makes fish `for` loops behave like most other shells. Fixes #1935 * Remove redundant line 2017-09-09 12:14:26 +08:00			`####################`
			`# For loop control vars available outside the for block`

use new `logmsg` and `set --show` in tests 2017-08-05 04:33:47 +08:00			`####################`
			`# Comments allowed in between lines (#1987)`

			`####################`
			`# Backslashes are part of comments and do not join lines (#1255)`

			`####################`
			`# Verify $argv set correctly in sourced scripts (#139)`