On 11Jul2007 21:14, Harald Kirsch <[EMAIL PROTECTED]> wrote:
| Changing a variable in a parent process, can never influence variable in
| a child process *which is already running*.
|
| Consequenly your only options are
| a) indeed completely start FVWM anew or
| b) use the built in functionality SetEnv.
I take the latter approach myself. Of course, normally I don't need to
feed environment updates to FVWM. But sometimes I want to change a
setting across the board, for all new windows and shells etc.
To this end I have two special arrangements in my shell environment.
First, at each prompt my shell contrives to source ~/var/env.sh,
a file with VERY FEW variable assignments that I really want to stick
everywhere.
Second, I have a shell function called setenv() (I don't use csh so this
name is available) that sometimes I invoke like the csh setenv command.
If I give it a -g option ("global") it also appends the setting to
the env.sh file _and_ passes the setting to my active FVWM.
Regarding the latter, I have FVWM start the FvwmCommandS module thus:
Module FvwmCommandS
and have setenv() pass the variable to FVWM by saying:
FvwmCommand "SetEnv $var $value"
where $var is the variable name and $value its new value (suitably
quoted).
Cheers,
--
Cameron Simpson <[EMAIL PROTECTED]> DoD#743
http://www.cskk.ezoshosting.com/cs/
These peoples' daily routines have subtly altered. Where before they
would have performed the following actions on reaching the department:
a. Enter building; b. scurry along corridoor; c. turn on terminal in passing;
d. approach office; e. turn on kettle; f. run back to computer; g. logon;
h. run back to kettle; i. pour coffee; j. return to computer with
coffee; k. read news; l. start work;
they have now inserted a new command into the program at point b. "pull
Babs' ponytail"
- Babs <[EMAIL PROTECTED]> in alt.peeves
