At 13:50 -0600 8/21/12, Clark Goble wrote: About the use of 0x0D while editing ALL fioes. > >It would seem if you do want to make this a feature in the future simply have >a filter function you run the grep text through before passing it to your grep >functions. In that filter function simply replace '\n' with '\r'. Then expose >a checkmark in the Preferences that turns this filter's use on or off. I bet a >lot of people would appreciate it. >
There still is a BBEdit worksheet in the Bare Bones offerings. I'm still on OS 10.3.9 because of my SE/30 file server and that means I may miss some changes here. I run all kind of filters on documents that are open in bbedit worksheets. UNIX grep, sed, and homemade perl scripts that read new data from serial ports, for instance. One has to be sure the document has been saved. After that you select a few contiguous commands previously stored in the worksheet and poke ENTER. They operate on the text file as it appears in its stored state. When the operations terminate the bbedit application notices that the file has changed and politely offers to update the editing image in its UNICODE-16 format. The one frustration that I have is that worksheets do in fact use 0x0D line ends internally while they store their own disk images with 0x0A endings in Apple plist XML files. That makes it impossible to edit a worksheet using bbedit itself; there are mixed line ends in the file. MPW operating on that SE/30 or this 8500 works much better. I'm pretty sure that the official rule is that on a Macintosh \r is still supposed to be interpreted as 0x0A and \n is 0x0D. That is the way it was in some RFCs when MPW was the way Macs worked. They haven't been updated and it pays to be careful on OS X. -- --> A fair tax is one that you pay but I don't <-- -- -- 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. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
