fish-shell/tests/test1.err
Kurtis Rader ba53242b26 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-20 12:02:45 -07:00

48 lines
1.1 KiB
Text

####################
# Comments in odd places don't cause problems
####################
# Bracket expansion
####################
# Escaped newlines
####################
# Simple function tests
####################
# Ensure eval doesn't unnecessarily mess with the exit 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
^
####################
# 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)