> BTW, "type print" gives me "/usr/bin/print".
Yep. So make sure the shell running the script doesn't find
/usr/bin/print.
Method a) mv /usr/bin/print /usr/bin/print_hold
run demo
mv /usr/bin/print_hold /usr/bin/print
Method b) Remove /usr/bin from your PATH. But chances are that
the script will need something in /usr/bin.
Method c) mkdir /tmp/demobin
cd /usr/bin
for file in *
do
ln -s /usr/bin/$file /tmp/demobin/$file
done
rm /tmp/demobin/print
Then replace /usr/bin with /tmp/demobin in your PATH.
Run demo.
Method d) Find a directory earlier in your PATH than /usr/bin.
Let's say that is /bin.
ln -s /bin/echo /bin/print
Run demo.
Method e) mkdir /tmp/demobin
ln -s /bin/echo /tmp/demobin/print
PATH=/tmp/demobin:$PATH
Run demo.
Method f) Use a shell with a print builtin that handles -r.
ksh and zsh have a print builtin that handles -r.
Method g) Use a shell with aliases.
alias print=/bin/echo
Run demo.
Replacing a -r handling print with echo may or may not cause problems,
since your echo probably doesn't handle -r and will just output "-r"
to stdout. So keeping type from finding a print, or having it find
one that handles -r would be safer than replacing print with echo.
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
