On Wed, May 11, 2005 at 03:48:51PM +0200, martin f krafft wrote: > also sprach Bas Zoetekouw <[EMAIL PROTECTED]> [2005.05.11.1528 +0200]: > > > True. But before it will even be considered to make env standard, > > > the parameter problem would have to be solved. perl -w and /bin/sh > > > -e are just necessary. > > > > Just put "use warnings;" or "set -e" in the script. > > Yes, those work. I am sure there are examples where it does not. > > Why the stupid limitation to a single argument only anyway?
That made me also curious.
<manualpage>
ENV(1) User Commands ENV(1)
NAME
env - run a program in a modified environment
SYNOPSIS
env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...]
DESCRIPTION
Set each NAME to VALUE in the environment and run COMMAND.
</manualpage>
Not checked, but it seems to allow more parameters.
Does
#!/usr/bin env - perl -w
so, the extra hyphen, the trick?
Cheers
Geert Stappers
signature.asc
Description: Digital signature
