"Kees Zeelenberg" <[EMAIL PROTECTED]> writes:
> No, this is intended behaviour. Env changes only the environment for the
> command that may follow the environment changes. For example, "env
> GSPATH=d:\util gswin ... " sets temporariliy an environment variable GSPATH,
> which is then recognized by gswin.After executing gswin ..., the environment
> is as before.
But env by itself should display the environment. So
env one=one env
should display the environment (the second "env") after adding
one=one to it (the first "env"). And yet it does not.
Also, when used to execute a console program, the console display is
messed up - it's as if the program started by env is running in
parallel with the shell - a bit like the mess you get if you run a
command using START /B from the shell.
Paul.
--
In theory, there is no difference between theory and practice; In
practice, there is. -- Chuck Reid
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
