Persisting env vars in cmd windows
- From: "Richard" <RichardDummyMailbox58407@xxxxxxxxxxxxxxxxxxx>
- Date: 5 Nov 2006 13:55:12 -0800
I've got a .bat file that sets a number of symbols (environment vars)
that are useful in a number of other command windows associated with
one of several projects. Right now, I operate by
1 opening a command window
2 draging the name of the symbol-setting bat file into the new cmd
window and pressing Enter
3 draging the name of one of my utility bat files in the cmd window and
pressing Enter
4 proceeding manually entering other commands as needed.
I'd like to eliminate step 2 by invoking the symbol-setter at the
beginning of every other utility file. I tried this by using "cmd /c
symbol-setter.bat" to no avail. I believe that fails because the "cmd
/c" command starts a new session in which to set local env. vars and
then ends, never communicating with the invoking session.
The best solution I can conceive of is to manually write a .reg file
appropriate to each project in which I want persistant env. vars, thus
only needing to invoke that once at the inception of a project, maybe
with another one to delete all such entries should the project
ultimately be destroyed.
Any comments?
Regards,
Richard
.
- Follow-Ups:
- Re: Persisting env vars in cmd windows
- From: GO
- Re: Persisting env vars in cmd windows
- From: Pegasus \(MVP\)
- Re: Persisting env vars in cmd windows
- Prev by Date: Re: Removing programs from Startup
- Next by Date: Re: Invalid boot.InI file, Booting from C:\winnt\
- Previous by thread: SMART: HDD Failure Is Imminent
- Next by thread: Re: Persisting env vars in cmd windows
- Index(es):
Relevant Pages
|