fish-shell/tests/vars_as_commands.in

# Test that using variables as command names work correctly.

$EMPTY_VARIABLE
"$EMPTY_VARIABLE"

set CMD1 echo basic command as variable
$CMD1

set CMD2 echo '(' not expanded again
$CMD2

# Test using variables with the builtin decorator
builtin $CMD1

# Test implicit cd
set CMD3 /usr/bin
$CMD3 && echo $PWD

exit 0
don't print internal token in error message Attempting to execute something like `exec "$test"` results in a fish internal token (a Unicode private use char) being printed in the resulting error message. That's obviously not desirable as well as confusing. Fixes #3187 2016-07-06 13:33:32 +08:00			`# Test that using variables as command names work correctly.`

Allow variables in commands Syntax highlighting for these coming in next commit. Fixes #154 2018-08-26 16:41:45 +08:00			`$EMPTY_VARIABLE`
			`"$EMPTY_VARIABLE"`

			`set CMD1 echo basic command as variable`
			`$CMD1`

			`set CMD2 echo '(' not expanded again`
			`$CMD2`

Fix builtin $var expansion A special case added for #1252 needed adjustment. Fixes #5639 2019-02-11 06:14:48 +08:00			`# Test using variables with the builtin decorator`
			`builtin $CMD1`

Allow variables in commands Syntax highlighting for these coming in next commit. Fixes #154 2018-08-26 16:41:45 +08:00			`# Test implicit cd`
			`set CMD3 /usr/bin`
			`$CMD3 && echo $PWD`
don't print internal token in error message Attempting to execute something like `exec "$test"` results in a fish internal token (a Unicode private use char) being printed in the resulting error message. That's obviously not desirable as well as confusing. Fixes #3187 2016-07-06 13:33:32 +08:00
			`exit 0`