On Feb 16, 2007, at 5:07 PM, Doug McNutt wrote:
Try the grep search from Terminal or a BBEdit worksheet.
BBEdit always uses \r for line endings internally. In an
AppleScript or search and replace you have to use \r to make things
work. Actually I think BBEdit now uses 16 bits per character
internally but it's still a 0D and not a 0A or one of those other
unicode line ends.
The endings are changed back to the selected values on a save so
files on disk should be what you expect.
Thanks for the clarification on that Doug. I suppose there is
explanation of that somewhere in the BBEdit documentation, but I
think it would be helpful to add some info on this subject to the
"Help > Grep Reference" section. It seems natural to assume that
you'd be able to change the line endings and then search for them.
Is there any possibility that FORTRAN code is creating files with
mixed line ends? It would be surprising in a FORTRAN source file
but quite possible as the result of a FORTRAN execution especially
if the program is reading data from an external instrument.
I really doubt that my Fortran code would create mixed line endings,
but it's possible that something unexpected is happening because my
compiler (Absoft) is really for a PPC Mac and is running on the Intel
machine courtesy of a patch that has not been thoroughly tested. The
next release is due soon and will be Intel-native.
Eric
--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
