Dear, k a k @ c i s c o . c o m.
Please don't set the From: header to [EMAIL PROTECTED], it confuses others.
Setting it to [EMAIL PROTECTED] would be ok.
On 18 Apr 2002 13:44:46 -0400, [EMAIL PROTECTED] wrote:
>
> Ahh, you are putting the whole script _IN_ the config file?
>
> I think what Dominik meant was the return value needs to stay under
> 1022, maybe I'm wrong, can someone clarify?
No, the return value is completely ignored in PipeRead.
> The way I do it it to keep a script dir in my path and call them like this:
>
> PipeRead "addExecutableOnMenu BrowserPopup opera galeon konqueror mozilla netscape
>cnetscape"
>
> Where addExecutableOnMenu is it's normal readable self sitting somewhere in
>~/somewhere:
>
> #!/bin/bash
> #
> #
> MENU="$1"
> shift
> while [ "$1" != "" ]; do
>
> which $1 2> /dev/null | {
> read fullpath
> if [ "$?" = "0" ]
> then
> echo "AddToMenu $MENU $1 Exec $fullpath"
> fi
> }
> shift
> done
>
>
> So if I have a script over 1024 it will fail even if it's sitting in an external
>file?
Yes, of course this is a good solution. The solution in the topic does not
use separate shell scripts, it embeds the script in 1 line:
PipeRead `for browser in opera galeon konqueror mozilla netscape cnetscape; do
fullpath="`which $browser 2>/dev/null`"; if [ -n "$fullpath" ] then echo "AddToMenu
BrowserPopup $browser Exec $fullpath; fi; done`
This can't currently exceed 1Kb.
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
