Good { morning, afternoon, evening },

We're working on an update to BBEdit 11 which will add some new features and 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 the previous pre-release build. 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.1.2 (3741)   (2015-06-29)

This build includes changes from the previous pre-release build, as listed here: <https://groups.google.com/d/msg/bbedit/YA4iPLPhkFw/6eUD82VKGREJ>.

Additions
---------

o   (none in this build)

Changes
-------

o   (none in this build)

Fixes
-----

*   [309089] Fixed crash which would occur when using "Save As" to
    save a file whose automatically generated default name was longer
    than 255 characters.

*   [309074] Fixed bug in which sub-line differences computation
would take too much time and take too much memory, and crash on
    extremely large comparisons which would cause it to run out of
    memory.

*   File comparison for sub-line differences can now be cancelled,
    in cases where it takes long enough to matter.

*   Fixed a lurking memory leak which would occur after various text
    transformations and when computing sub-line differences.

*   [309030] Fixed a crash which would occur when deleting a large
quantity of items from inside of a folder that's represented as
    an application menu (such as Scripts or Clippings).

* [308987] Fixed bug in which making edits at certain points in a very large CSS document would lead to incorrect recalculation of
    syntax coloring information, with resulting coloring mistakes
    until the document was closed and reopened.

*   [308981, 309009] Made a change to improve performance and reduce
    memory consumption while making automatic state snapshots; this
    generally shouldn't be noticeable unless you have a tremendous
    number (hundreds) of documents open.

*   [309024] Fixed bug in which attempting to comment (via insertion
    point placement) a single line in a language for which only block
    delimiters were available would end up doing nothing. (Examples
    of this would be HTML or CSS.)

=end=

The package can be downloaded from our web server:

    <https://s3.amazonaws.com/BBSW-download/BBEdit-11.1.2_3741.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