Jim Correia wrote: >If you need to run files with unix line endings on the Mac, you can >start the run from within BBEdit (5.1 or greater, commercial version) >and it will detect the situation and insert some magic between you and >MacPerl to make the right thing happen, so you don't ever have to >convert the line endings on disk if you don't want to. I just did this and it works great! I opened a file on my Linux box from within BBEdit on my Mac (opening files via FTP rocks!). I checked and as expected it had Unix newlines. Using the [camel-picture] menu, exported to cgi on my Mac web server and it ran. Scientists always run controls: I then did a "Save As..." onto my Mac. This preserved the Unix newlines. I switched to MacPerl and opened it. As expected, it looked bad (one run-on line with little box characters.) I saved it as a cgi anyway, and as expected, it failed. </Control> One suggestion: When I did the export, it replaced the filename with a random number which is less than wonderful but ok, but it also added by default the .acgi file suffix. .acgi is often bad thing. The default should, IMHO, be .cgi Again, for the cognoscente, this is no biggie, you just ignore the suggested filename, but I think it is the wrong default as it sends the naive down a dangerous path. -David- David Steffen, Ph.D. President, Biomedical Computing, Inc. <http://www.biomedcomp.com/> Phone: (713) 610-9770 FAX: (713) 610-9769 E-mail: steffen@biomedcomp.com ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org