> > NewAddToMenu menu_name item_name [(item_options)] ItemAction > > NewAddToMenu menu_name (menu_options) > > This is almost exactly what I had in my mind. I though about: > > + item_name [item_default_action] [(item_options)]
That's the original thing I had in mind except that might cause some parsing weirdness. Take this menu entry for example: + "Wisqlite" Exec echo '(add tcl83; add sybase11; wisqlite)' | /bin/csh -s & It might be difficult to have it decide whether the ( )'s here are in reference to options or to a piece of a command string. > They may, but should not really stay parts of the labels. They cause > excaping problems with '&' and several other symbols. There are currently > problems/inconsistencies with how fvwm escapes '&', if there is underline > in the item, '&' should be escaped as "\&", otherwise as "&&"! This is a > real problem for menu autogenerating scripts. > > I think we should only support this in the old compatibility syntax when > the default action is specified as-is and not as an option. I guess it really wouldn't be that difficult to keep some form of backwards compatibility in there no matter what we go with... I agree that these options really shouldn't stay part of the labels though. I still dislike how hard-to-read having the options in the labels tends to make the config files. Daniel -- /\\\----------------------------------------------------------------------///\ \ \\\ Daniel Henninger http://www.vorpalcloud.org/ /// / \_\\\ North Carolina State University - Systems Programmer ///_/ \\\ Information Technology <IT> /// """--------------------------------------------------------------""" -- 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]
