Re: menu: suggestions - extending the menu files

1998-01-02 Thread Karl M. Hegbloom
> "joost" == joost witteveen <[EMAIL PROTECTED]> writes: joost> Uhm, there's a slight problem with ifeq($visable, joost> "false",...). If we assign booleans to the string variables joost> ($visable etc are essentially strings), then I'd prefer joost> them to by default to have

Re: menu: suggestions - extending the menu files

1998-01-02 Thread joost witteveen
> The menu package is amazingly flexible. :-) (thanks!). (And, BTW, I agree with all that you said and I didn't repeat). > > wait="t" or wait="nil" - some programs exit after output, but I want > > to read it first. (like how mc says push a key after it runs a cmd.) > > This is a good idea, a

Re: menu: suggestions - extending the menu files

1997-12-27 Thread Joey Hess
Karl M. Hegbloom wrote: > It occurs to me that the menu files ought to have fields for: > > Xresources to get `xrdb -merge'd when the program is launched. (lazy eval) > (and removed perhaps, on the delete window hook? Does the X server gc?) Sounds hard to do. > Menu font, color, icon, a p

menu: suggestions - extending the menu files

1997-12-20 Thread Karl M. Hegbloom
It occurs to me that the menu files ought to have fields for: Xresources to get `xrdb -merge'd when the program is launched. (lazy eval) (and removed perhaps, on the delete window hook? Does the X server gc?) Menu font, color, icon, a predicate for when it's greyed off (think scwm) XTerm