fish-shell/tests/checks/features-ampersand-nobg-in-token1.fish

#RUN: %fish --features=ampersand-nobg-in-token -C 'set -g fish_indent %fish_indent' %s

echo no&background
# CHECK: no&background

echo background&
# CHECK: background

echo background &
# CHECK: background

wait

echo no&bg | fish_features=ampersand-nobg-in-token $fish_indent --check
echo $status #CHECK: 0
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 18:19:32 +08:00			`#RUN: %fish --features=ampersand-nobg-in-token -C 'set -g fish_indent %fish_indent' %s`
Make '&' only background if followed by a separating character This is opt-in through a new feature flag "ampersand-nobg-in-token". When this flag and "qmark-noglob" are enabled, this command no longer needs quoting: curl https://example.com/thing?foo=bar&duran=duran Compared to the previous approach e1570a4 ("Let '&' only separate as the first char of a word"), this has some advantages: 1. "&&" and "&>" are no longer affected. They are still special, even if used between tokens without spaces, like "echo bar&>foo". Maybe this is not really better, but it avoids risking to annoy users by breaking the old variant. 2. "&" is still special if at the end of a token, like in "sleep 1&". Word movement is not affected by the semantics change, so Alt-F and friends still stop at every "&". 2021-06-30 01:30:27 +08:00
			`echo no&background`
			`# CHECK: no&background`

			`echo background&`
			`# CHECK: background`

			`echo background &`
			`# CHECK: background`

			`wait`
Teach fish_indent about our feature flags So it can handle syntax changes that call for different formatting. 2021-07-11 02:08:34 +08:00
			`echo no&bg \| fish_features=ampersand-nobg-in-token $fish_indent --check`
			`echo $status #CHECK: 0`