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 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.
Change notes for the previous pre-release build are available
here: <https://groups.google.com/d/msg/bbedit/7MsCXNSdbdI/c2ET4z3zfbIJ>.
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.6 (3315) (2013-10-09)
Additions
---------
o (none in this build)
Changes
-------
o (none in this build)
Fixes
-----
* File icons in disk browsers are now colored appropriately when
the file/folder has a label (according to the file system
metadata). This also includes single-tag items when running on
10.9.
* [279296] Fixed crash which would occur when trying to
compute a
default file name extension and the Languages preferences
contained one (or more) custom extension mappings with no
extension.
* Fixed crash which would occur when trying to apply an Automator
workflow as a text filter, caused by Automator returning
something other than what it used to.
* [279393] There's a new expert pref:
`defaults write com.barebones.bbedit
ShowFullPathsInSearchResults -bool YES`
It's off by default, but turning it on will cause the
application to
display the full (home-relative) path for files listed in search
results windows.
* If [Dash](http://kapeli.com/dash) is installed, BBEdit will now
use it for "Find in Reference", in preference to any predefined
or custom reference lookup URLs. This can be controlled via
an expert
preference, on a per-language basis if desired:
`defaults write com.barebones.bbedit
UseDashForReferenceLookups -bool NO`
`# turn off Dash support entirely`
`defaults write com.barebones.bbedit
UseDashForReferenceLookups_Ruby -bool NO`
`#turn off Dash support only for Ruby`
You could, if you wanted, turn off Dash support by default
and then enable
it for specific languages, e.g.
`defaults write com.barebones.bbedit
UseDashForReferenceLookups -bool NO`
`# turn off Dash support entirely`
`defaults write com.barebones.bbedit
UseDashForReferenceLookups_C++ -bool YES`
`#turn on Dash support only for C++`
* Added a table of contents and internal jump points to the Expert
Preferences help.
=end=
The package can be downloaded from our web server:
<http://pine.barebones.com/seeding/BBEdit-10.5.6_3315.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].
