Good { morning, afternoon, evening },

We're working on an update to BBEdit 10.5 to address a few recently reported issues.

Note that this is a _pre-release_ version. The intent is to fix bugs and address areas of improvement based on what our customers have reported. However, since the software is at this point not fully tested, there _may_ be bugs and regressions. If this prospect makes you nervous, then sticking with the public release versions is your best course of action. Nobody will be offended if you choose to do so; you're under no obligation to install and use anything but a public release. :-)

Following is a summary of the changes in the software since the last public release. The change notes are organized into additions, changes, and fixes, and are annotated where appropriate with case numbers. So if you recognize a number corresponding to a support case that was opened for you, you can now verify that it's been fixed correctly. Please take the time to review the changes before using the new build -- it'll be worth your time.

One final note: If you run into a bug in a pre-release version, PLEASE DO NOT REPORT THE BUG TO THE LIST. This includes asking about whether others have seen the same problem. Instead, please send a bug report to <[email protected]> and we will deal with it there. This will help us keep the list discussion on topic and productive for all list members.

============================================================================

version 10.5.8 (3349)   (2014-01-07)

Additions
---------

o   (none in this build)

Changes
-------

o   (none in this build)

Fixes
-----

*   [284200] Fixed crash which would occur at startup when the
    `Application Support/BBEdit/Clippings` folder was empty and not
writeable, or when `Application Support/BBEdit/Clippings` did not
    exist and the `Application Support/BBEdit` folder was not
    writeable.

* [241406] When previewing an unsaved or untitled document with an
    external helper, BBEdit now writes the temporary file out using
    the same line breaks as the document, rather than using the
    internal representation. This improves compatibility with preview
    helpers that aren't web browsers (e.g.
    [Marked](http://marked2app.com)).

*   [284642] Fixed bug in which bz2-compressed files were not read
    correctly.

*   [284660] Fixed bug in the Fortran scanner in which it was
    confused by certain keywords appearing out of context.

* [284859] Fixed crash when using "Find in Reference" with no document open.

*   Updated copyright year.

*   Fixed a bug in the Fortran function scanner in which
    subroutine/function ends weren't correctly detected when the
    qualifying identifier didn't end exactly at a line break.

*   Fixed bug in which the functions and folds could be out of sync
    if the document contents were reloaded from disk or reverted.

*   Restored the previous order of startup so that crash recovery
    takes place after sleep state restoration.

*   [266007] Fixed bug in which references to documents previously
    opened in a project were not properly resolved relative to the
    project document itself, which would create confusion in cases
    where the project was moved or copied.

*   [271968, 284900] Fixed cosmetic glitch in which the pop-down
arrow icon in the header of disk browsers would sometimes draw in
    the toolbar area.

=end=

The package can be downloaded from our web server:

    <http://pine.barebones.com/seeding/BBEdit-10.5.8_3349.dmg>

Enjoy,

R.
--
Rich Siegel                                 Bare Bones Software, Inc.
<[email protected]>                      <http://www.barebones.com/>

--
This is the BBEdit Talk public discussion group. 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>

--- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].

Reply via email to