At 15:15 +0100 10/10/06, [EMAIL PROTECTED] wrote: >I've got Unix line endings selected in BBEdit. When I copy two lines of text >from BBEdit, and store them from the pasteboard in Unix into a file (using >pbpaste on the command line), I get lines separated with 0D (that's 0D as in >hex 13) characters. But if I do it from some other places, such as a man >page, the lines are separated by 0A characters. Does BBEdit use 0D for Unix >LF? (?!)
My theory is that BBEdit uses 0D for everything in memory while editing is in progress. The chosen line ends are applied during rewriting to a file on disk or elsewhere. The need to make the changes during initial reading of a file may contribute to the observed slowness on very large text files. It is painfully evident with worksheets which actually contain UNIX commands. The structure on disk is your lines with 0D endings embedded as a single item in a .plist file that uses 0A ends for the XML wrapper. Picking up lines from a worksheet with AppleScript will result in 0D line ends. There is no way to "show invisibles" in a way that allows one to see what is actually present in a source file that came from elsewhere. A continuing problem to me is that I acquire files - like BBEdit worksheets - that contain divers endings and I have to work with them. MPW on this 8500 running OS 9.1 remains my fall back for such things. BBEdit's dump file command helps but you can't edit things that way. -- Applescript syntax is like English spelling: Roughly, though not thoroughly, thought through. -- ------------------------------------------------------------------ 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]>
