Good morning folks,
We're currently working on a feature update to BBEdit 12, which
includes a number of new features, as well as fixes for
previously reported issues.
Testing is currently underway, and we have a stable pre-release
version ready for use.
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. :-)
Complete change notes to date for all the pre-release builds in
this cycle are available here:
<https://s3.amazonaws.com/BBSW-download/notes-12.6.txt>
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.
============================================================================
version 12.6 (412013) (2019-01-09)
* This version of BBEdit requires macOS 10.12.6 or later. It will
not run on previous versions of macOS or Mac OS X.
* BBEdit is now a sandboxed application.
“App Sandboxing” is a term that refers to a collection
of security
technologies built in to macOS. Sandboxing is intended to protect
you and your data by limiting the operation of applications
to their
intended use, which in turn makes it harder for malicious software
or accidental misuse to cause data loss or damage to your computer.
One of the core concepts of App Sandboxing is that BBEdit,
as a
sandboxed application, is not allowed to use any of your
files or
folders without your explicit permission. You can grant this
permission in one of a small number of ways, including (but not
necessarily limited to):
- Asking BBEdit to open a file from the Finder by
double-clicking it;
- Dragging a file from the Finder on to BBEdit’s
application icon;
- Using BBEdit’s “Open…” command to choose a file
or folder.
However, as an advanced developer tool, BBEdit frequently requires
access to files or folders that that you may not have specifically
asked it to open, for safe and legitimate reasons:
- If you have located BBEdit’s application support
folder in
Dropbox or iCloud Drive, BBEdit needs to be able to figure
out where the folder actually is, and be able to use that
location;
- When opening a document, BBEdit needs to know:
- whether the file is under revision control with Git or
Subversion;
- whether there are one or more .editorconfig files which
control editor options for the file;
- whether any ctags data is available to support BBEdit’s
completion and "Find Definition" features;
- When previewing a file with unsaved changes, BBEdit
needs to
be able to write a temporary file out in the same directory,
so that relative links within the file remain correct;
- If you have turned on “Make Backups” in the Text Files
preferences, BBEdit needs to be able to write backup and
auto-recovery files in the same directory as the file being
saved;
- The “Open File by Name” feature needs to be able to examine
all possible directories that may contain files for which
you're searching, including some that you may never have
used before in BBEdit;
- Many dialog boxes in BBEdit which allow you to choose a file
or folder give you the choice of directly entering a file
path;
...and many more similar cases.
Without unrestricted access to your files and folders, many of
BBEdit’s most useful features, from the basic to the most powerful,
won't work at all; or they may misbehave in unexpected
ways. At the
very least, this hinders your ability to work done.
In order to resolve this fundamental conflict between
security and
usability, we have devised a solution in which BBEdit
requests that
you permit it the same sort of access to your files and
folders that
would be available to a non-sandboxed version.
For this reason, the first time you start BBEdit, it will
prompt you
to allow this access. The prompt will not be repeated; so
if you
decline to allow this access and later reconsider, go to the
Application preferences, and click on the "Allow" button in the
"Sandbox Access" section.
This in no way compromises your security or that of your computer
while using BBEdit, but does allow BBEdit to function at
its fullest
potential.
If you have been using a previous non-sandboxed version, your
existing settings and support folder contents are
unaffected by this
change.
Additions
---------
* Added a "Folders" submenu to the main application menu. This
menu gives quick access to BBEdit's application support folder
(the same list that is available in the Folders tab of the Setup
window). This is useful on its own merits, but is of particular
relevance in the application sandbox, in which support folders
can be buried in locations that are not easily accessible from
the Finder.
Changes
-------
* Made a change so that double-clicking anywhere in a
syntax-colored number will select the entire number, even
if it
contains a decimal point (which would otherwise be a word break).
* When running on macOS 10.14.1 or later, BBEdit now uses built-in
OS support for performing operations which require privilege
escalation, namely authenticated saves and (if escalation is
necessary) installation of the command-line tools.
* If the application resets the evaluation period, the splash
screen at startup will now advise you of this, via an
alert. (The
evaluation period gets reset when we've made significant changes
to the application which we believe would warrant a full trial.)
* Reworked the way BBEdit runs AppleScripts from the built-in
Scripts menu and other sources, for sandbox compatibility
and to
resolve various longstanding issues.
AppleScripts are now run in a separate process, which means
that any
previous differences in scripting behavior as the result of running
a script within BBEdit or from the Script Editor should be
a thing
of the past.
* If "Keep folders on top when sorting by name" is selected in the
Finder's preferences when BBEdit starts up, FTP browser windows
will now obey the option and behave accordingly.
Fixes
-----
* Modernized the internals of the #! script and Unix executable
runner, SFTP operations, and shell worksheets.
* Rewrote the internals of the built-in software updater to be
sandbox-friendly. (This does not apply to Mac App Store builds.)
* Updated the privilege escalation internals (used for
authenticated saves and command-line tool installation when
running on macOS versions prior to 10.14.1) for compatibility
with app sandboxing.
* Fixed bug in which the initial line number in "Go To Line" would
not take into account any folded ranges in the text.
* Fixed bug in which the Windows palette didn't re-sort when the
active document changed in an open window, or when certain other
changes were made to open documents or windows.
* Fixed bug in which the font smoothing expert preferences were
inappropriately allowed to disable font smoothing while printing.
* Fixed bug in which type-to-select in FTP browser windows would
behave unpredictably, because as it turned out, the system was
helpfully attempting to match in columns other than the "Name".
(Thanks to [Daniel Jalkut](https://www.red-sweater.com/) for
figuring this out. Go buy one of his products or [become a member
of his podcast](https://coreint.org/membership/).)
* Fixed bug in which SCSS interpolation structures (`#{...}`)
would confuse the SCSS block parser and result in incorrect fold
generation and function listings.
* Fixed bug in which folders that were twisted open when saving
state for a disk browser (when quitting) were selected when the
disk browser window was reopened at startup.
* Fixed crash which could occur if a document was closed while
processing a (possibly accidental) command-click (the
gesture to
open an URL).
* Fixed bug in which Command-Shift-click on an URL did not
open it
in the background, as it should have. (The intended
behavior is
to open the URL in its designated application while keeping
BBEdit active.)
* Fixed bug in which certain inline-input edits which involved
deleting in-progress input at the beginning of a hard line
in a
soft-wrapped document would leave the insertion point in the
wrong place, and cause unexpected arrow-key navigation
afterwards.
* Made a change to improve text encoding detection in XML files
whose filename extensions didn't map to XML. As long as the file
has an exact "`<?xml `" at the very beginning, it should
now be
detected correctly.
* Fixed bug in which the Swift parser would get confused by
certain sequences of escaped quotes inside of a string.
* Made a couple of changes to make the application take less time
when quitting in the normal case (a "sleep", when state and
documents are autosaved).
* Fixed crash which would occur when trying to use "Preview in
BBEdit" to preview a document whose backing file had been
deleted.
* Fixed bug in which the "Flatten Hierarchies" option for Find
Differences when comparing folders didn't actually work.
* `#script#` directives in clippings can now use a home-relative
path to the script to be run, e.g. `#script ~/path/to/some/script.scpt#`.
* Made a change so that text in the status/navigation bars, line
number bar, and other locations is darker in inactive windows
when "Increase contrast" is turned on on the system accessibility
preferences (and a light appearance is in use).
* Fixed bug in which comparing two temporary windows (such as
generated by the results of Hex Dump) with identical names would
cause the title of the Differences window to have slashes in
front of those names.
* Fixed bug in which keyboard focus in the Markup Builder panel
was in the wrong place in cases where the tag being edited
had no
attributes, and Full Keyboard Access (Keyboard system
preferences) was set to "Text boxes and lists only".
* Made a change so that Find Differences results which are not
selected will appear using the Differences color, but less
intense. This should be more visible than the previous light
gray.
*fin*
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.
The package can be downloaded from our web server:
<https://s3.amazonaws.com/BBSW-download/BBEdit-12.6_412013.dmg>
Enjoy,
R.
--
Rich Siegel Bare Bones Software, Inc.
<[email protected]> <http://www.barebones.com/>
Someday I'll look back on all this and laugh... until they
sedate me.
--
This is the BBEdit Talk public discussion group. If you have a
feature request or need technical support, please email
"[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <https://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].
Visit this group at https://groups.google.com/group/bbedit.
