http://steveo.syslang.net/envv.tar.gz
If I could inject one (hopefully) final thought... :-)
The above URL (happens to be in perl) is a script that I use heavily to
set environment variables in my login environment. The purpose of it is
to edit environment variables whose values are colon seper
Good catch. I was typing most of it in on the fly.
At 12:49 PM 1/16/2003 -0500, John Abreau wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Charles Reitzel <[EMAIL PROTECTED]> writes:
[snip]
> BEGIN
> {
>$HomeDir = '/usr/local/foo';
>$Fo
By and large, they do. The parent/child process issues are the same.
There a couple Resource Kit utilities that update the "master"
environment. Likewise, with the appropriate permissions, you can directly
update the Registry entries where the environment values are kept - either
system wide
On Thu, Jan 16, 2003 at 05:52:24PM +, David Cantrell wrote:
> On Thu, Jan 16, 2003 at 12:30:36PM -0500, Ron Newman wrote:
> > Unix folks are used to these limitations on how you can use
> > environment variables. Do things work the same way in Windows?
>
> It's quite some years since I last
On Thu, Jan 16, 2003 at 12:30:36PM -0500, Ron Newman wrote:
> Unix folks are used to these limitations on how you can use
> environment variables. Do things work the same way in Windows?
It's quite some years since I last used Doze, but I think it works the
same way. Except that there's ways ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Charles Reitzel <[EMAIL PROTECTED]> writes:
[snip]
> BEGIN
> {
>$HomeDir = '/usr/local/foo';
>$Foo = 'foo';
>@Bar = ( qw(Foo Baz Bar) );
>%Baz = { Foo => $Foo, Bar = \@Bar };
> }
[snip]
The
Unix folks are used to these limitations on how you can use
environment variables. Do things work the same way in Windows?
___
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
On Thu, Jan 16, 2003 at 09:59:52AM -0500, Ron Newman wrote:
> You *could* have the perl script set all of the environment
> variables, then exec a new shell.
Abigail came up with quite a neat move involving a double exec written
up on Fun With Perl list. In hir own words,
From: abigail[at]foad.or
On Thu, Jan 16, 2003 at 11:51:46AM -0500, Charles Reitzel wrote:
> At 09:51 AM 1/16/2003 -0500, [EMAIL PROTECTED] wrote:
> >That's a bummer.
> >TMTOWTDI becomes NCD -> No Can Do
>
> If it is any consolation, it isn't Perl's fault. It is inherent in the
> nature of parent/child processes. The ch
On Thu, Jan 16, 2003 at 09:59:52AM -0500, Ron Newman wrote:
> You *could* have the perl script set all of the environment
> variables, then exec a new shell.
You *could* use the perl shell, but that's crazy talk.
--
David Cantrell|Reprobate|http://www.cantrell.org.uk/david
W
At 09:51 AM 1/16/2003 -0500, [EMAIL PROTECTED] wrote:
"Hanes, Philipp" wrote:
> Probably not.
Hi Philipp, how're things?
That's a bummer.
TMTOWTDI becomes NCD -> No Can Do
If it is any consolation, it isn't Perl's fault. It is inherent in the
nature of parent/child processes. The child c
You *could* have the perl script set all of the environment
variables, then exec a new shell.
___
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
"Hanes, Philipp" wrote:
> Probably not.
That's a bummer.
TMTOWTDI becomes NCD -> No Can Do
> What's the script like?
it's a hodgepodge of several scripts, actually.
each one is intended to support a specific tool,
setting environment variables, paths, etc.
We'd like to make them more intellige
13 matches
Mail list logo
