> > > > Also, I have a lot of decors similar to this: > > > > > > > > AddToDecor FvwmCons HilightColor black green > > > > > > > > which apparently should change to > > > > > > > > AddToDecor FvwmCons HilightFore black, HilightBack green > > > > > > > > This looks like a simple enough transformation to have been done > > > > automatically, and the script did convert a standalone > > > > > > > > HilightColor black yellow > > > > > > > > to > > > > > > > > Style "*" HilightFore black, HilightBack yellow > > > > > > > > but it did not convert HilightColor within AddToDecor or even comment > > > > on what should be done. Is there something more to it? > > > > > > No, the script apparently does not handle commands buried in > > > decors. Just change it manually. > > > > After changing them manually, I get: > > > > [FVWM][execute_function]: <<ERROR>> Command can not be added to a decor; > > executing command now: 'HilightFore black, HilightBack green' > > [FVWM][execute_function]: <<ERROR>> No such command 'HilightFore' > > > > and 6 more sets, one for each decor that tries to do this. All > > borders get the black/yellow highlight. > > The error message is fully correct, only five *Style commands are > accepted in decors. Please see the man page (search for AddToDecor), it > includes the correct usage example, convert your configuration similarly.
This turns out to be a nice simplification. The only reason I had multiple decors in 2.2.4 was to get different highlight colors. Now that the highlight colors go directly in the Style command, all the extra decors can go away. -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
