A colleague just alerted me to the fact that text files I sent him
recently have a carriage return (\r or CR) line ending instead of the
newline (\n or LF) they used to have. These are files created in a
Fortran program under OS X 4.8. It may be that this change occurred
when I started working on a MacBook Pro a few months ago. The reason
I'm writing this list about it is the very odd behavior of BBEdit
(8.6 and 8.6.1) with regard to line endings.
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. If I grep for \r
it finds each line ending. So there seems to be a discrepancy between
what BBEdit says the line endings are and what's actually there.
Then, if I change the line endings to Mac style (\r) and then back to
Unix style, the file stays with Mac style line endings. In other
words, I can't seem to change the line endings using BBEdit.
Since my colleague on a Unix workstation sees the \r line endings
also, I think they really are there, But I cannot understand where
they're coming from, nor why I cannot change them with BBEdit. I must
be missing something rather gross here.
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]>
