Good morning folks,
We're currently working on another maintenance update to BBEdit
12 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. :-)
Complete change notes to date for all the pre-release builds in
this cycle are available here:
<https://s3.amazonaws.com/BBSW-download/12.6.2_Notes.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.
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.
Here is the list of changes made since the previous pre-release build:
============================================================================
version 12.6.2 (412057) (2019-03-18)
* This version of BBEdit requires macOS 10.12.6 or later. It will
not run on previous versions of macOS or Mac OS X.
Additions
---------
o (none in this build)
Changes
-------
* Adjusted the built-in FTP client to use the `MLSD` command to
obtain directory listings, if the server supports it. If not,
BBEdit will fall back to more primitive methods. This corrects
cases in which _some_ FTP servers do not return complete
listings, most notably omitting files whose names begin
with a
period (`.`).
On some servers, however, `MLSD` works, but does not return
the same
results as the older methods. Therefore, there is a method to
disable use of MLSD:
```
# only for "foobar.example.com"
defaults write com.barebones.bbedit
FTPDisableMLSD:foobar.example.com -bool YES
# only for servers in "example.com"
defaults write com.barebones.bbedit
FTPDisableMLSD:example.com -bool YES
# global preference
defaults write com.barebones.bbedit FTPDisableMLSD -bool YES
```
We recommand that that you disable MLSD per host whenever possible,
rather than globally or per-domain.
**Note:** In some cases, the server may be configured to
never list
files whose names begin with a period (`.`). In that case,
there is
nothing you can do in BBEdit to have these files listed in FTP/SFTP
browsers, and you will need to contact your server
administrator or
hosting service to have the server configured appropriately.
Fixes
-----
* [NFR] [368601] Fixed beta regression in which a 100093 error
would get reported when trying to prepare script files for
execution.
============================================================================
version 12.6.2 (412055) (2019-03-18)
* This version of BBEdit requires macOS 10.12.6 or later. It will
not run on previous versions of macOS or Mac OS X.
Additions
---------
o (none in this build)
Changes
-------
* [DOC] Non-App Store builds of BBEdit will no longer prompt for
sandbox access at startup. However, it is still possible that
sandbox access is required in order for certain behaviors
to work
correctly.
In particular, the OS will unilaterally decide to "quarantine"
certain files when you ask BBEdit to open them from the command
line; and there are likely to be other misbehaviors caused by
assumptions that the OS makes when running a sandboxed application.
If this poses a problem for you, go to BBEdit's "Application"
preferences, and check the "Sandbox access" indicator. If
the status
indicates "not allowed", then use the "Allow" button to
grant BBEdit
sandbox access. This will prevent the OS from adding
quarantine to
files opened from the command line, and may work around
other OS
misbehaviors.
Fixes
-----
* [NFR] [368516] Fixed a beta regression in which the downloaded
disk image for self-update on a non-admin account was quarantined
by the system, such that the OS would refuse to launch the
application after installing from the dmg.
* [NFR] [DOC] [368475] Worked around an OS sandboxing behavior in
which using the `bbedit` command-line tool to open an executable
shell script (`foobar.sh`) in BBEdit would add the quarantine
attribute to the file. This in turn made the file unusable from
anywhere until manually removing the quarantine attribute.
* [367959] When using "Run in Terminal" or "Run in Debugger"
for a
file with a `#!` line, BBEdit will no longer attempt to guess
which tool should be used to run the file, and will simply ask
the shell to run it. That way, custom `#!` lines (e.g. for custom
Python installations) will work as expected.
*fin*
The package can be downloaded from our web server:
<https://s3.amazonaws.com/BBSW-download/BBEdit-12.6.2_412057.dmg>
Enjoy,
R.
--
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.
