mirror of
https://github.com/fish-shell/fish-shell.git
synced 2024-11-23 08:13:08 +08:00
ba53242b26
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
49 lines
1.1 KiB
Plaintext
49 lines
1.1 KiB
Plaintext
|
|
####################
|
|
# 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)
|