Rajat Patni wrote:
> So is there no soln. to my problem?
Maybe if you described what you are trying to do (big picture) we can
find an alternative for you. It is generally considered 'bad manners'
for any program to change the operating environment of its parent, but
there are obviously exceptions to this general rule (Global environment
variables, Files, etc) that cannot be avoided.
Alternatives:
- Don't use a 'program', but use shell aliases/etc (which will
obviously both run in the context of the shell you are in, but also be
shell specific)
- Have the program launch a new shell which would have the modified
environment.
- Set global variables which are read by the command in which you want
to have this 'changed environment'.
---
Russell McOrmond, Internet Consultant: <http://russell.flora.org/work/>
�Researching Group Calendar:
http://www.cyblings.on.ca/projects/calendar/
--
To unsubscribe, send mail to [EMAIL PROTECTED] with the body
"unsubscribe ilug-cal" and an empty subject line.
FAQ: http://www.ilug-cal.org/help/faq_list.html
