On Wed, 01 Sep 1999 23:39:49 +1000 Brian Keck <b.keck_at_trl.telstra.com.au> wrote
concerning 'Re: FVWM: dynamic nummanagers? ':
> On Wed, 01 Sep 1999 09:17:24 -0400, Dan Boger wrote:
> >On Wed, 01 Sep 1999 20:02:37 +1000 Brian Keck <b.keck_at_trl.telstra.com.au> wrote
> >> ...
> >> that's right (no visible iconmanager for host BOD when I'm not running
> >> an xterm on BOD)
> >well, one way I can think of implementing this is having the xterm
> >spawning function start a iconman for that host, and another (perhaps
> >run with FvwmCommand from the .logout) close that iconman when the
> >last xterm of that host closes.
> >...
>
> Thanks, but I think that's more or less what I was trying to avoid.
>
> The critical thing seems to me to be need for a nummanagers setting.
> The only way I could see of fixing things is to have the spawning
> function make a new .fvwm2rc with an incremented nummanagers, & restart
> fvwm2. This would be pretty ugly, undressing & dressing all the
> windows, & not all that fast on the old machines I have. I was hoping
> there might be an alternative to specifying a literal value for
> nummanagers in .fvwm2rc.
>
> Have I missed something?
>
I don't think you'll need to restart fvwm - you can use the Read
command to read the new iconman (say FvwmIconManBOD) configuration,
then just spawn the new module. and when you're done, Close
FvwmIconManBOD should make it go away. Or perhaps I'm missing
something?
Dan
--
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 Wed Sep 01 1999 - 08:50:33 BST