At 1:36 AM -0600 1/10/2002, Ken Williams wrote: > >How is Terminal supposed to know what kind of line endings you want? I >create lots of text files in both formats. I don't think the solution >lies in fixing anything about Terminal. I think I agree with Chris, it >would be nice if perl were a little more agnostic about line endings in >its scripts.
But in this case, the problem wasn't with Perl. It was tcsh (most likely) on the BSD side of things that couldn't figure out what executable to run the shell script with. It couldn't figure out a path to something called: /usr/bin/perl^Mprint "Perl on Mac OS X\n"; In the /usr/bin/ directory, there isn't an executable called perl^Mprint with an embedded carriage return in its name. Even when Perl is able to handle multiple line ending formats, you'll run into this problem. (And receive the error "../mac_perl.pl: Command not found.") In Chris' example, I think vim used Mac or DOS line endings rather than unix ones, most likely based on its fileformats settings, http://www.vim.org/html/options.html#'fileformats' Terminal and the pasteboard, it turns out, were behaving well. It was, as is usually the case with this sort of problem, an issue with the text editor. -Charles [EMAIL PROTECTED] -- Charles Albrecht Euonymic Solutions [EMAIL PROTECTED] P.O. Box 300623 C>303.619.7596 F>978.334.3061 Denver, Colorado 80203-0623
