BBEdit 12.6.2 Release Notes
BBEdit 12.6.2 contains fixes for reported issues.
For details on all the new features and enhancements available in BBEdit 12, please see the release notes for BBEdit 12.6, BBEdit 12.5, BBEdit 12.1, and BBEdit 12.0, or browse the release notes archive.
For detailed information on using any of BBEdit's features, please refer to the user manual (choose "User Manual" from BBEdit's Help menu).
Important: Please make sure that you have read the BBEdit 12.6 change notes, as there are significant changes from previous versions.
BBEdit 12.6 requires Mac OS X 10.12.6 or later, and is compatible with macOS 10.14 "Mojave".
If you are using macOS 10.13 "High Sierra", please make sure that you have updated to the latest available OS version (10.13.6 or later).
If you are using macOS 10.14 "Mojave", please make sure that you have updated to the latest available OS version (10.14.3 or later).
This update does not include any feature additions. The following behavior changes have been made in existing features:
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.
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
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.
Made a change to the EditorConfig internals to improve performance during large-scale batch operations, such as multi-file search.
Made a change to improve the performance of the filename-to-extension language mapper during large-scale batch operations (such as multi-file search).
Made a change to reduce overhead when guessing a file's text encoding during large-scale batch operations such as multi-file search.
Made a change to resolve confusion caused by an OS behavior, which left the default location for the Save panel pointing at the top level of the startup disk after granting sandbox access. This in turn left the panel pointing there by default when saving a new document.
Fixed a bug in which the sidebar width was not correctly restored in windows which were in full screen mode when the application was quit.
Change the “
file filter” and “
folder filter” syntax in the
scripting terminology to “
file_filter” and “
respectively, so that recorded scripts actually compile.
Made a change to fix a probable crash which would occur when doing a batch site update while one or more files from the site were open for editing.
Renamed the “
BBAuthOperationsXPCService” helper to
BBEditPrivilegedOperationsHelper”, so that it's less scary for
Fixed bug in which Add/Remove Line Numbers took much longer than it should have in cases where it took long enough for a progress dialog to be necessary; and corrected the titles in the Add/Remove Line Numbers progress dialog.
Fixed bug in which the sidebar width was not restored correctly when restoring application state at startup, when the "Automatically show" sidebar setting was "Always".
Worked around an OS misbehavior in which temporary files written out for running #! scripts from within the application (when the document you want to run has unsaved changes) were quarantined, and so attempts to run them using the shell would fail.
Adjusted the default width of the sidebar so that it's not quite so wide.
The "Deploy Site" command for projects will now skip over Google
site verification files when preprocessing (based on whether the
file has "
google-site-verification:" at the very start).
Fixed a bug in generation for
which an absolute path was always generated for files within the
site's specified "templates and includes" directory.
In cases where a site project's "Templates and Includes" folder is inside the project's "Local Site Root" folder, the contents of the templates folder will no longer be preprocessed nor uploaded when deploying.
Fixed a bug in which opening the Functions palette with keyboard focus in the Live Search box would result in the palette being devoid of items.
Fixed regression in which touching a file's modification date outside of the application did not cause its displayed modification date to update in the editing view status bar.
Fixed a bug in which printing always ignored the time stamp setting, and used the printing date in the page header.
When using "Run in Terminal" or "Run in Debugger" for a file
#! 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.
Added a few CSS selector names to the built-in keyword list.