TruerWords Logo

Search TruerWords

Sign Up  Log On

“Bare Bones Released BBEdit 9.2”

From: Seth Dillingham In Response To: Top of Thread.  
Date Posted: Thursday, May 7, 2009 6:02:17 PM Replies: 1
Enclosures: None.

BBEdit 9.2 was released today.

(Sorry about having two BBEdit-related posts in a row like this. I have other things to talk about too, trust me. I'm just warming up again.)

I played a small part, again. Most of my time was spent on the brand-new Lasso module. There are 168 changes in the official change notes. (There were actually a lot more than 168 changes, trust me.) The excerpt listed below includes those I'm particularly happy about or with which I was personally involved.

The blue stuff, below, is what I worked on or was somehow directly involved with.


  • ✫ BBEdit now has a “Sleep” command. ✫

  • Lasso is now a fully supported language, with syntax coloring, functions listed in the function popup, and automatically generated fold points.

  • There’s a new color setting in the Text Colors preference: “Numeric Constants”. This can also be adjusted on a per-language basis in the appropriate language’s settings (in the “Languages” preferences).

  • Added a feature to the language module interface for giving the module control over resolution of include file references.

  • The Menus preferences now has a group of commands so that you can assign keyboard equivalents to operations in FTP/SFTP browsers, if desired.

  • There’s a new setting in the “Editing” tab for language-specific preferences (Preferences -> Languages): “Tab width”. Edit the value here to set a language-specific value for the default tab width. (I — and probably others — requested this.)

  • ✫ BBEdit now implements the necessary hooks so that the following JavaScript functions now work when using “Preview in BBEdit”: window.alert, window.confirm, window.prompt, window.onbeforeunload ✫

  • Disk browsers can now explore tarballs (.tar, .tar.gz, .tgz files). When an eligible file is in the listing, it will have a disclosure triangle next to it. Twist it open to reveal the files and directories within. As with other items displayed in disk browser listings, you can view files in the editor view, or double-click them to open in a separate window for editing.


  • ✫ The internal mechanics and UI presentation for recent items have been overhauled. ✫

    I love this one, as the redesigned "Open Recent" menu item is much more usable.


  • Fixed a bug in the ActionScript function parser. No longer tripped up by a function return type of * (which is the explicit way of typing something as “untyped”).

  • Fixed a bug which allowed ActionScript’s get to be recognized as a function-starter in JavaScript files (similar to the function keyword).

  • Fixed possible cause of a crash related to populating the function popup in JavaScript files.

  • Fixed missing fold widgets for fold ranges containing a single line break.

  • Fixed crash when JavaScript functions with assigned names, such as[bat] = function() {...}, were not in a recognized/expected form.

  • Fixed bug in which using “Save As” did not change the document’s language if the default was something other than “(none)”. This change also addresses a bug in which the document’s language wasn’t recalculated if the file’s name changed on disk.

  • A variety of changes have been made to reduce application startup time.

  • Fixed a bug in the Ruby module which would cause a multi-line, general delimited input string (%+string+) to fold incorrectly (the closing fold point was one character too soon).

  • Fixed a bug in the Ruby module where Begin/End blocks could cause fold points to be be placed at seemingly random places in the document.

  • Fixed a bug in the Ruby module where complete for or while loops, written on a single line and within curly braces, could throw off the folding for the entire document.

  • Fixed a bug in the TeX module in which a $math$ section within a {required param}, where the $math$ section contained a closing curly brace (e.g. caption{foo $i_{0}$ foo}), would confuse the parser. This tended to manifest as incorrect autofolds and improper indentation in the function popup.

  • The Ruby module will no longer detect regular expressions as the first token immediately after a string or another regular expression. This resolves a syntax coloring bug found with the syntax used by the Merb framework (which uses an overloaded ”/” method.)

Now go buy a copy. Or two. Please. More sales at BB means more work for me. (Blah blah blah |BEdit Disclaimer|)

Discussion Thread:

There are no trackbacks.

is Seth Dillingham's
personal web site.
Truer words were never spoken.