Files
fish-shell/doc_src
Johannes Altmanninger 80e30ac756 Always treat brace at command start as compound statement
For backwards compatibility, fish does not treat "{echo,hello}" as a compound
statement but as brace expansion (effectively "echo hello").  We interpret
"{X...}" as compound statement only if X is whitespace or ';' (which is an
interesting solution).

A brace expansion at the very start of a command 
is usually pointless (space separation is shorter).
The exception are cases where the command name and the first few arguments
share a suffix.

	$ {,1,2,3,4}echo
	1echo 2echo 3echo 4echo

Not sure if anyone uses anything like that.  Perhaps we want to trade
compatibility for simplicity. I don't have a strong opinion on this.

Always parse the opening brace as first character of a command token as
compound statement.
Brace expansion can still be used with a trick like: «''{echo,foo}»

Closes #11477
2025-05-11 22:00:43 +02:00
..
2025-04-11 15:11:22 +02:00
2022-09-17 21:31:06 +08:00
2025-04-11 15:11:22 +02:00
2025-04-11 15:11:22 +02:00
2025-05-03 19:26:07 +08:00
2025-04-12 12:09:08 +02:00
2025-04-29 13:51:18 +02:00