Re: FVWM: Argument Passing?

From: Thomas A. Gardiner <gardiner_at_pas.rochester.edu>
Date: Fri, 14 Jan 2000 12:25:58 -0500 (EST)

On Fri, 14 Jan 2000, Dan Espen wrote:

>I'm thinking too.
>
>I have yet to figure out what your asking about.
>
>Is this in reference to scripts launched by the Exec command,
>or FvwmScript, or some other kind of script?

I have a script in my $HOME/bin/ directory which I execute from my
.xsession with a command something like

exec $HOME/bin/RunWM --FvwmFoo

This is essentially a reworked version of the RunWM script used by RedHat
to start the window manager from xdm. The argument FvwmFoo causes fvwm2
to be started with the FvwmFoo decor.

In order to switch decor to FvwmBar the AnotherLevel package does a
restart calling the script RunWM.FvwmBar which is a symbolic link to
RunWM. The script RunWM then checks to see how it was called or if it was
called by the name RunWM.FvwmBar or RunWM.Foo or what have you and chooses
the appropriate decor.

The annoying part is that every time I want to add another decor I have to
create another symbolic link, edit the RunWM script, as well as a few
other routines.

There are two simple ways to get around this.

1) Pass an argument to the script.

2) Have two commands executed in sequence from a single menu selection
which essentially will do

echo FvwmBar > $HOME/.wm_style
exec RunWM

This is not the preferred alternative though since the RunWM script will
end up doing

cat $HOME/.wm_style

meaning that the two commands need to be executed in order.

Tom

--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Jan 14 2000 - 11:28:45 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:50 BST