At 18:56 -0700 2/16/07, Eric Bergman wrote: >BBEdit is set to use unix line endings (\n or LF) by default and BBEdit shows >that unix line endings are being used when I open them. But if I do a greg >search for \n the search fails.
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. 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. BBEdit doesn't support mixed line ends. It decides which one comes something like first and treats any others as garbage. BBEdit's Hexdumps are your friend. <ftp://ftp.macnauchtan.com/Software/LineEnds/FixEndsFolder.sit> might also be helpful. -- --> Life begins at ovulation. Ladies should endeavor to get every young life fertilized. <-- -- ------------------------------------------------------------------ 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]>
