Mikhael Goikhman <[EMAIL PROTECTED]> writes: > On 07 Jun 2003 22:18:20 -0400, Dan Espen wrote: > > > > WindowStyle does make sense as a separate command. > > When it gets processed, it gets turned into a style > > with an ID so that if there is a restart, it can get reapplied > > to the window. > > > > In the case you give above: > > > > Next (Class XTerm) WindowStyle NoButton 6 > > > > I don't see how that can replace the Style command, unless > > we also saved the "Next" part of the command. > > Even then, its not quite the same, Next only executes > > when it matches something. The current Style command > > doesn't have to match anything to work. > > Well, the original idea that removes Style command completely was: > > AddToFunc StyleFunction I Next (Class XTerm) WindowStyle NoButton 6 > > and StyleFunction is applied on all new windows.
Something like an "AddWindowHook". > But I would not discuss this idea now. I am sure we will have many > discussion after 2.6.0. :) Even if we don't implement this idea and > implement "Style (Class XTerm, Resource rxvt)" syntax instead, still > I think it is good to have 2 separate commands: Style that ignores > window context and WindowStyle that requires window context. Agreed. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
