-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 18/07/12 04:09 PM, William Hubbs wrote:
>
> The other approach, which is on the bug, still has this issue,
> e.g.
>
> /etc/init.d/foo command1 arg1 arg2 command2 arg3 arg4 command3
> arg5
>
> gets pretty ugly pretty quick. which arguments go with which
> commands is subject to interpretation.
..i don't see how...? anything to the right of [command] but before
{[other-command],$END} is an argument to [command] ...
ie, the above would roll out to:
/etc/init.d/foo command1 arg1 arg2 && \
/etc/init.d/foo command2 arg3 arg4 && \
/etc/init.d/foo command3 arg5
(assuming subsequent commands do not execute if the previous one fails
now, which tbh I have no idea about)
It's not the most pretty syntax ever, but given i doubt it will be
humans running such a commandline I don't see the issue with this..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iF4EAREIAAYFAlAHGZUACgkQ2ugaI38ACPCXNAD8DR8qHFOQnGCt2W+sOXYJDsXu
H6pnnFt09ssbuKjKHZwA/2pZxnGnXJTWGVdPySoIsJtr8Pe6Za9yeL4yQ0WHPocr
=G3H9
-----END PGP SIGNATURE-----
