Re: Re: Modifying the environment

Similar idea, I just think about something, but I never try it. It
should work.

In your .xinitrc or whatever you use, call a script that look like that: 

---->
#!/bin/sh

while [[ 0 == 0 ]]; do
    ~/.environment.sh
    wmaker
done
<----

It will make wmaker restart automaticly after it exit, after it load
your environment variable.  That way, on your wmaker menu, the "Exit"
will restart wmaker after execution of ".environment.sh", you can rename
the "Exit" menu item to "restart" and make another "Exit" menu item that
will kill the script that call wmaker from the infinite loop.

It look like a weird solution, seems to do exactly what you need. (if
it's work :p )

good luck.

Martin


On Thu, Jun 16, 2005 at 04:25:55PM +0100, Glenn Morris wrote:
> Jim Knoble wrote:
> 
> >     (d) Don't use the WindowMaker executable directly.  Write a wrapper
> >         script around .../wmaker which sets environment variables,
> >         either within the script or by sourcing a file such as
> >         ~/.environment.sh.  Then, use something like 'selectwm':
> 
> That's an interesting idea, thank you.
> 
> So, basically, there's no existing functionality in WM for doing this,
> but there are various tricks one can try.
> 
> I sort of feel that any program that's used to launch a bunch of other
> programs ought to offer an easy way to modify its (and hence their)
> environment(s), as shells do. Maybe I'll submit a feature request
> using the funky WM bug tracker... well, if it existed I might... ;)
> _______________________________________________
> INFO: https://windowmaker.org/lists/listinfo/wm-user
> ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
> FAQ: http://windowmaker.org/faq.html
_______________________________________________
INFO: https://windowmaker.org/lists/listinfo/wm-user
ARCHIVE: https://windowmaker.org/lists/archive/wm-user/
FAQ: http://windowmaker.org/faq.html