in the late 1900s it was said:
> -> Picture this:
> -> I have a standard FvwmButtons module called fb1. On this
> -> button set I have one button named "Servers" with a server
> -> icon on there.
> ->
> -> Clicking on this button will spawn a new FvwmButtons
> -> module named "fbServers" which will contain icons for
> -> each of our development servers and one button named
> -> "Close", or a button containing a "back arrow" icon.
> ->
> -> Clicking on the "back arrow" or "Close" button would
> -> kill that particular instance of the FvwmButtons module
> -> named "fbServers".
>
> look at
>
> http://www.giccs.georgetown.edu/~ric/software/fvwm/wharf
Yes, it was mentioned that I was describing the FvwmWharf
behavior by another reader.
Two reasons I do not want to go that route:
1. Too lazy to learn new syntax for the Wharf module
and get it to look and feel like my FvwmButtons
module.
2. The KillModule command description I origionally
gave was a generic one and the FvwmButtons example
was just that; and example.
One could extend the use of such a module to kill
particular instances of *any* module.
Note that I am not trying to be deficult and/or trying
to push idea of development of such a command. I was
simply pondering if there was an elegant way for me to
do what I wanted to do.
A few work.arounds were suggested with:
`ps blah | grep blah | cut blah | kill blah'
command....which would obviously work fine, though
carry with it quite a bit of overhead (execv processes
and pipe stuff to one another, etc etc).
Thanks all for their informative replies!
I appreciate every comment I received! :)
Patrick ...
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Jul 31 1998 - 21:58:46 BST