S5 vs. BBEdit 8.2.1
Published 19 years, 2 months pastJust a quick note for any of you who might be both a BBEdit user and an S5 author: BBEdit 8.2.1, the latest update, will crash if you try to open any valid S5 presentation (I don’t know what happens with invalid files). Apparently there’s a bug in BBEdit’s XHTML scanner that the S5 file structure triggers. Version 8.2, which you can get from the Barebones FTP site if you don’t still have it locally, does not have the same bug, and will edit S5 files without any trouble.
The folks at Barebones are aware of the problem and have indicated that a fix will be in the next maintenance release of BBEdit. For now, if you want to edit S5 files in BBEdit, stick to 8.2.
(And if anyone wants to take a crack at helping out with the problems in S5 1.1rc1, see my earlier post on the subject. Thanks!)
Comments (7)
Just be aware of another bug in BBEdit 8.2: if you have ftp bookmarks with user names or passwords that contain “unusual” characters, like @, your keychain will be destroyed. No fun at all, I can tell you. I’m back to version 8.1 for the time being.
Concerning S5 Safari bug – just add ‘return false’ as last statement in keys()
You know, I’ve had some other problems with BBEdit 8.2.1, which really surprises me. This is the first time I’ve ever considered downgrading (downdating?) on a BBEdit release, and I’ve been using BBEdit for over half a decade.
You can always write to tech support if you’re having problems. :-)
Rich: I already did; that’s why I knew it was a bug in the XHTML scanning routines as opposed to something else. In fact, it’s why I posted at all. Although I was pretty confident that the problem was with 8.2.1 and not my system, I figured I’d make sure with you guys before posting anything.
As part of that correspondence, I passed along mention of the keychain problem Roger mentioned in his comment, just in case he hadn’t already mailed the same address.
Eric: Sorry for the contextual goof; my remark was for Roger and Mark.
BBEdit 8.2.2 fixes the bug that caused this problem, as shown in the release notes and confirmed by personal testing of the new version. Let there be great rejoicing.