At 08:54 -0500 10/1/09, Rod Buchanan wrote:
And I snipped it all

The problem I have with BBEdit, and I'm limited to OS 10.3.9 for other reasons, 
is that there is absolutely no way that BBEdit will allow me to work with files 
that have mixed line ends for perfectly good reasons.

It is most important to me because I need to handle ASCII text files that are 
the result of connections to divers electronic measurement devices that offer 
line ends which include all three options but get mixed up in the download 
process.

But recently I have tried to intercept the error output from the well-known 
/usr/bin/curl tool.  It uses carriage returns, \r in UNIX systems,  to return 
to the left side of a window with the deliberate intention to overwrite the 
previous line with new data.  When it issues a \n code it expects the shell to 
drop down a line. It's much like the ASR 33 that I once learned to lov except 
that teletype demanded \r\n for that purpose (well. . . the \r and \n were 
really 5 bit codes).

It is impossible to use BBEdit to intelligently interpret a redirected output 
file produced for debugging. My guess, unconfirmed, is that BBEdit looks at the 
first few line ends and assumes all the rest will be the same.

Yes. I can preprocess with perl scripts but other software simply accepts  all 
possible line ends, leaves them in the file, and then allows editing and 
eventually  saves of the file that manage to preserve line ends so that what 
came is what goes out.

-- 
--> The message came to Abraham that he would beget a son. Sarah, who was 
behind the door, laughed. <--

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the 
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/bbedit?hl=en
If you have a feature request or would like to report a problem, 
please email "[email protected]" rather than posting to the group.
-~----------~----~----~----~------~----~------~--~---

Reply via email to