On Wed, Sep 01, 1999 at 11:39:49PM +1000, b.keck_at_trl.telstra.com.au wrote:
> 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.
Hm, do you have a small sample configuration with more than one
manager?
Bye
Dominik ^_^
--
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.com
--
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 - 09:56:34 BST