Good { morning, afternoon, evening },

We're working on an update to BBEdit 11.0 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 pre-release build <https://groups.google.com/d/msg/bbedit/I9HW_65-Hk8/jzAOtT1wr4oJ>. 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 11.0.1 (3483)   (2014-11-04)

*   BBEdit now requires OS X 10.8.5 or later. It will not run on any
    previous version of the OS.

Additions
---------

    o   (none in this build)

Changes
-------

    o   (none in this build)

Fixes
-----

*   [298013] Fixed bug in which the sidebar width for project
    documents was not restored as it should have been when opening
    the project.

*   Fixed bug in which the sidebar in editing and project windows
    would grow and shrink when the window width changed.

*   [250338] Fixed bug in which certain constructs in C source files
were not colored correctly if they followed a number without any
    intervening whitespace.

-   [298105] Fixed hang in Markdown scanner when a document
    started with blank line, a `>`, and a tab. (But only
    on new moons in August and October)

-   Fixed a bug in the syntax coloring of Markdown documents,
    where text would be colored as though it were `PRE` formatted,
    when in fact the indentation was not enough to trigger
    that formatting. Not that whitespace is significant, because
    we all know it's not. But we'll pretend.

*   [NFR] [298468, 298546] Fixed a regression in which Update Site
    Images would duplicate `width` and `height` attributes in image
    tags. (This was actually symptomatic of a bug in the reworked
    low-level code.)

-   Updated generator app version in the help book (mostly to
    eliminate matches for "BBEdit 10" while searching the help :-))

*   [298173] Fixed a bug in which Markdown link text in list items
    was not colored as it should have been.

*   [289053] The default internal character classes now include word
    characters that lie outside of the normal US-ASCII range; among
    other things this allows text completion to work in documents
    where the language is other than "none".

*fin*

=end=

The package can be downloaded from our web server:

    <http://pine.barebones.com/seeding/BBEdit-11.0.1_3483.zip>

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