On 25 Aug 2001 01:33:00 +0000, Mikhael Goikhman wrote: > > I fixed the problems above and some more, except for ^ and @ in Popup > (they work in Menu with --reuse). I think it should be fixed in fvwm. > > Currently when MissingSubmenuFunction is called the argument is not passed > correctly. Double ^^ and @@ are not converted to single ones as should be.
Correction. This part is ok, my mistake. ^ and @ should only be escaped in AddToMenu, not in DestroyMenu, Menu, ChangeMenuStyle. Now, directories with ^ or @ work well for me. Still I think this syntax is bad for several reasons: AddToMenu [EMAIL PROTECTED]@^blue^ Compare with a syntax without escaping problems: AddToMenu StartMenu "Start" Title linux-menu.xpm SidePic blue SideColor I also tried to make files and dirs with $ and \ work in the script. This works ok, except for file names like $v or $$v. I am checking the possibility that there is a bug of escaping special vars in + lines. It is impossible to make it work with all shells since they escape $ and \ differently in strings, I only consider bash and company. "ExecUseShell /bin/tcsh" currently does not work in very rare cases. > Also if Popup "my name" contains spaces, 2 parameters are passed. The > whole name may be read in $*, but $* is not good for fvwm-menu-directory > (unlike $0 .. $9 if you use $* you should know how the function is called), > the best solution is to implement what the man page says: > > I.e. the name is passed to the function as its > first argument and can be referred to with "$0". This is still a problem. Regards, Mikhael. -- 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]
