Mikhael Goikhman <[EMAIL PROTECTED]> writes: > On 17 Mar 2002 17:47:27 -0500, Daniel Henninger wrote: > > > > My only other suggestion was going to be a completely different menu > > style of: > > > > StartMenu "AppMenu" ( SidePic "ninja.xpm", SideColor blue ) ... > > EndMenu > > > > Where + was simply a "continue the previous line" so you could split > > things up. > > This can't work with the current command philosophy. There are no > multiline commands, all commands are executed immediately one by one. > There are many reasons for this. But I will only list some problems with > the sample above. > > Suppose a user forgot one EndMenu or one StartMenu. Or added some commands > inside a menu definition (it is possible now). What to do? Ignore the menu > definition? Ignore the non menu lines until the end of file? Close EndMenu > automatically? But if this can be done automatically, why EndMenu is > needed?
I hadn't been paying much attention until now. Getting rid of start/end was one of the reasons for the fvwm1/fvwm2 break. -- Dan Espen E-mail: [EMAIL PROTECTED] 444 Hoes Lane Room RRC 1C-214 Phone: (732) 699-5570 Piscataway, NJ 08854 -- 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]
