"Zack Weinberg" <[email protected]> writes:

> [..]
>
> runs `ls` with `LC_ALL=C` in the environment, without changing the value
> of LC_ALL for any subsequent command.  Csh doesn't have that feature,
> but the `env` utility fakes it:
>
>     env LC_ALL=C ls
>
> [..]

This is neat piece of trivia.  And the explanation was well written and
easy to follow :)

> I also plan to mandate env support the -S option, which is not in POSIX,
> but without it anyone who wants to point a #! line at awk without knowing
> the absolute path of the awk implementation is up a creek.

Busybox's env does not have the -S.  So making it mandatory will prevent
fairly popular distribution (alpine) from complying, and compliant
scripts will not work on it.  Would it not be better to recommend
writing a simple shell wrapper instead?

Maybe it would be worth it to propose the -S to the Austin Group?

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

Attachment: signature.asc
Description: PGP signature

Reply via email to