On Sat, Oct 09, 2004 at 07:58:08PM -0400, Parv wrote: > in message <[EMAIL PROTECTED]>, > wrote Parv thusly... > > > > in message <[EMAIL PROTECTED]>, > > wrote fvwm-w thusly... > > > > > > On Sat, Oct 09, 2004 at 02:19:36AM -0400, Parv wrote: > > > > > > Style * FPLenient \ > > > > , FPClickRaisesFocused , FPClickRaisesUnfocused \ > > > > , FPClickDecorRaisesFocused , FPClickDecorRaisesUnfocused \ > > > > , FPClickIconRaisesFocused , FPClickIconRaisesUnfocused \ > > > > , FPGrabFocus , FPReleaseFocus \ > > > > , FPAllowRaiseClickFunction \ > > > > , ClickToFocusPassesClickoff \ > > > > , ClickToFocusRaises , MouseFocusClickRaises \ > > > > , FPFocusByFunctionWarpPointer \ > > > > , MouseFocus > > > > > > You should be aware that the maximum command length in fvwm is > > > 1024 bytes. If you keep adding styles to this list you might > > > hit that limit at around 30 lines in the style definition. > > > > I thought about that (as converting the above syntax w/ line > > continuations to "Style * " for each line undid some problem that > > turned out to be a red herring). > > Not a herring after all! After breaking up the above Style thusly ... > > Style * FPLenient \ > , FPClickRaisesFocused , FPClickRaisesUnfocused \ > , FPClickDecorRaisesFocused , FPClickDecorRaisesUnfocused \ > , FPClickIconRaisesFocused , FPClickIconRaisesUnfocused \ > , FPGrabFocus , FPReleaseFocus \ > , FPFocusByFunctionWarpPointer \ > , FPAllowRaiseClickFunction > > Style * ClickToFocusPassesClickoff , ClickToFocusRaises \ > , MouseFocusClickRaises , MouseFocus > > > .... in 2.5.12, WindowList is making the list in the desired order just > like it does in 2.5.10 (w/ or w/o both combined). Combining the two > styles does cause the problem (in 2.5.12). Thanks Dominik.
That feels lika a bug int the style merging code. I still don't know exactly what behaviour you see. In which order do you get the window list: - with 2.5.10, - with 2.5.12 and a sing style line, - with 2.5.12 and multiply style lines? With the config you posted earlier, I get exactly the same (correct) order with 2.5.10, 2.5.12 and current CVS, regardless of whether I split the style lione or not. -- > BTW, comma placement has no effect on the order. No, and that will never change. > I understand that the situation may change in future as Dominik > has pointed out in this thread and also previously in various > threads. When (if) I change it, it won't affect the order. Style lists without commas will simply stop working. Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED]
pgpJHZQKgho3Q.pgp
Description: PGP signature
