The version of BBEdit available in the Mac App Store does not support authenticated saves (the ability to save changes to files that you do not own) and does not include the command-line tools, in order to comply with Apple’s submission guidelines.
Command-line tools: Any customer who purchased BBEdit 10 from the Mac App Store may use the following package to install the command-line tools on their system. (This package is only for use with Mac App Store copies of BBEdit 10, and is not suitable for use otherwise.)
BBEdit command-line tools installer: download
Note: BBEdit 11 is not available in the Mac App Store; if you would like to upgrade from a BBEdit license purchased in the Mac App Store, you can do so here: BBEdit Upgrades for Mac App Store Customers.
BBEdit 11 requires Mac OS X 10.9.5 or later, and is compatible with OS X 10.11 “El Capitan”. It will not run on any earlier version of Mac OS X.
El Capitan’s Split View feature requires that the OS allow BBEdit to enter that mode, which it currently does not. We regret that this is not a feature we can add, nor a limitation that we can work around ourselves. In order for Split View to work in BBEdit, Apple will need to add support for BBEdit by making a change to the OS.
If you have a developer account, we encourage and recommend that you file a bug report with Apple, requesting that they correct this situation. File a bug report here. Note that if you file a bug using the developer bug reporter, you should attach a System Information report, and follow Apple’s bug reporting guidelines.
If you don’t have a developer account, you can instead send comments to Apple using their OS X feedback form.
No technical details are required; all that Apple needs to know is that you expected Split View to be usable in BBEdit, and that you found it nonfunctional.
BBEdit supports opening and editing files written in most left-to-right writing systems, including non-Roman languages such as Japanese, Chinese, and Korean.
However, BBEdit does not support editing content in right-to-left languages such as Hebrew and Arabic. (You may also encounter inconsistencies when working with languages that routinely employ conjunct characters, such as Devanagari.)
If you have a large number of files which you need to convert from one line ending type to another, we recommend that you create a Text Factory with a single “Change Line Endings” action, and apply that text factory to any folder(s) containing the files you wish to modify.
Dealing with large files presents no intrinsic problems for BBEdit. However, BBEdit is a RAM-based editor, and it uses system memory to hold open files. BBEdit also represents open documents as Unicode, which uses two bytes for each character. At this writing, the largest single file you will be able to open in BBEdit will be in the neighborhood of 800-900 megabytes (838,860,800 characters). Files in the range of half a gigabyte (500-600M) will pose no particular challenge (though the range of actions you can perform on such a file may be restricted).
Just hold down the Option key (the mouse cursor will change to a cross shape) and then drag to make a rectangular selection.
Please note the “Soft Wrap Text” option must be turned off in order to make a rectangular selection. (You can turn off soft wrapping in the current document via the Text Options popup in the toolbar, or in the Text Options sheet.)
Short Answer: Because they contain errors! :-)
Long Answer: BBEdit’s syntax checker is based on language templates generated from published DTDs and when it reports an error, the odds are good that the checker is correct.
If you don’t believe that it is correct in doing so, please check the most recent available on-line HTML references, and contact technical support.
We use Amazon’s AWS S3 cloud download service to serve updates (and many other downloads that we provide), and the IP address for “
s3.amazonaws.com” (the hostname for Amazon’s S3 service) may reverse-resolve to any one of a number of domains that also use this service.
Thus, this alert from Little Snitch is not reporting anything untoward — instead, Little Snitch is being diligent but inaccurate in not telling you the actual requested host name of the DNS lookup. In order to download and install updates using the built-in Check for Updates, you will need to give permission to access Amazon S3, even if the name that Little Snitch reports is not correct.
If you would like to verify this, you may do so as follows, using the Terminal application or a BBEdit shell worksheet:
Run this command:
In place of “
StrangeServerName”, substitute the name that LittleSnitch reported in its alert. For example, if the server name was “
assets.huffingtonpost.com”, run the command:
Note that in the “ANSWER SECTION”, you’ll see an entry with the server’s IP address. Note also that there are additional server names listed, including “
s3.amazonaws.com” and possibly other names in the
If you wish to verify further: Use that IP address in the following command:
dig -x a.b.c.d (substitute the actual address for “
a.b.c.d”). In the “ANSWER SECTION” you will see one of the Amazon host names (in the “
amazonaws.com” domain) that appeared in the previous command that provided the server’s IP address.