From: Cindy Parker on
Assume I start CommandPrompt with the current set of environment variables (and their values).

Then I change OUTSIDE some values of these environment variables or even add some new.

When I type now "set" then the old set of environemnt variables is visible.

How can I "refresh" the environment variables inside this CommandPrompt from the outside current (updated) state?
Of cause without having to enter all the changes again inside the CommandPrompt and without exit and restart
CommandPrompt (I want to maintain the history list of commands).

Cindy

From: Greg Russell on
In news:4c4f1253$0$7663$9b4e6d93(a)newsspool1.arcor-online.net,
Cindy Parker <cypy(a)live.com> typed:

> Assume I start CommandPrompt with the current set of environment
> variables (and their values).
>
> Then I change OUTSIDE some values of these environment variables or
> even add some new.
>
> When I type now "set" then the old set of environemnt variables is
> visible.
>
> How can I "refresh" the environment variables inside this
> CommandPrompt from the outside current (updated) state? Of cause
> without having to enter all the changes again inside the
> CommandPrompt and without exit and restart CommandPrompt
> (I want to maintain the history list of commands).

Are we supposed to guess how you changed the variables "OUTSIDE"? Did you
parse a script?

That would allow your independent command environment to parse the same
script and accomplish your stated need.

But if you used a GUI to change the variable values then you'll have to
manually enter them into the command session, or else restart a new one
which will violate your criteria.