Good { morning, afternoon, evening },

We're working on an update to BBEdit 11 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 previous pre-release build <https://groups.google.com/d/msg/bbedit/xRyzKn0MORI/6NBnyTHkcFsJ>. 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 <supp...@barebones.com> 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.3 (3507)   (2015-02-11)

Additions
---------

    o   (none in this build)

Changes
-------

    o   (none in this build)

Fixes
-----

*   Fixed bug in which attempting to save a zero-length file with
    Windows line breaks would report a -50 error.

*   The path controls in the Find Differences dialog box now have
    tooltips when appropriate.

*   [303097] Adjusted the "is text file" content check to
    pre-emptively rule out Photoshop files, which look enough like
    text files internally to pass the test. Any file which has a
nonzero HFS file type that is *not* `'TEXT`' or a relative is now
    ruled out in the "is a text file" test, in advance of any content
    checking. Together these two changes will prevent multi-file
    searching from finding text in files where it shouldn't.

*   [301848] Made some changes to make the default list of preview
    helpers more useful.

*   [303168] When examining a file to determine whether it is a Zip
    archive (for opening as well as when searching), BBEdit will
    first examine the file's UTI (Uniform Type Identifier)
    information; and if the UTI does not indicate that the file might
    be a Zip archive, filtering ends at that point. In some cases,
    this can lead to files being skipped that are in fact Zip
    archives, but which don't have conforming UTIs. To solve this
    problem, you can disable UTI checking:

`defaults write com.barebones.bbedit InspectUTIWhenFilteringZipFiles -bool NO`

    *Note:* Disabling UTI inspection means that BBEdit will _always_
have to open the potential Zip file to inspect its contents. This
    will slow down batch operations such as multi-file search/replace,
text factory application, and file filtering for projects and disk browsers when the directory being processed contains a lot of files that are potentially Zip archives (and not previously determined to
    be text files).

-   [303346, 303395] Fixed a bug in the Ruby module which would
    cause incorrect generation of fold points if an iterator ended
    with a "trailing if" or "trailing unless", such as:

    `a = b.c.select { |d| foo(d) unless d == nil }`

=end=

The package can be downloaded from our web server:

    <http://pine.barebones.com/rhombus/BBEdit-11.0.3_3507.zip>

Enjoy,

R.
--
Rich Siegel                                 Bare Bones Software, Inc.
<sie...@barebones.com>                      <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
"supp...@barebones.com" 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 bbedit+unsubscr...@googlegroups.com.
To post to this group, send email to bbedit@googlegroups.com.

Reply via email to