On Apr 27, 2010, at 9:24 AM, Rich Siegel wrote: >> A complete digest of the changes is available here: <http://www.barebones.com/support/bbedit/arch_bbedit95.html>
That link shows: >> If you are using the expert preference to save state in the document's >> resource fork (rather than in a central location), please note that the new >> format state data is not actually saved in a resource anymore - it is now >> written into an extended attribute, which you can verify from the command >> line using @xattr -l /path/to/some/f...@. I'm limited to OS 10.3.9 for other reasons so it doesn't matter right now but that scares me. I save BBEdit preferences for files in the resource fork with confidence that when I use a simple cp or perhaps an scp or ftp of my file to a Windoze or Ubuntu friend he will receive a faithful copy of the text without something else appended or even, perish the thought, some plist format that obscures the text with multiple line end characters as with a BBEdit worksheet. If I copy the file to a backup Macintosh server, using a resource-preserving method, will it open over a network with the preferences preserved? Please add some comments with some more details about the change. And tell me that @ sign in the command line above is only because I'm reading this using Classilla on Mac OS 9.1 which likely has problems with unicode. It looks like an AT sign in an email address to me. -- --> Give me liberty or give me Obamacare <-- -- 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.
