BBEdit 13.5.4

What's new in this version:

Changes:
- Changed the default location for the "BBEdit Backups" folder, from Documents into the application support folder proper. This avoids various bugs and misfeatures in macOS 11 that are triggered by having items in the Documents folder
- The previously supported locations are still supported
- As always you can get to this folder in the Finder by choosing "Document Backups" from the Folders submenu of the BBEdit application menu

Fixed:
- Adjusted the behavior of "automatically wrap files with long lines" so that it is less likely to do so on files that don't actually require it
- Added atomic to the keyword list for Objective-C/C++
- Fixed a bug in which using a status (or navigation) bar item's keyboard equivalent while it was open would cause unexpected behavior in the menu
- Fixed bug in which the Get Info panel showed incorrect information for the owner and group in the Permissions tab
- Fixed bug in which "Reload from Server" for a remote document would fail to correctly decode the data provided by the server in cases where the document itself had been reopened from a cached local copy during state restoration
- Undid a change intended to work around a macOS bug (FB8925588) because the change appears to trigger even worse behavior in the OS (namely, causing the OS to set up a new sandbox container and break symlinks to existing BBEdit support folders). The workaround has been refined so that the OS will not create a phantom "BBEdit" placeholder in your home directory. (If there is one there already, leave it alone - deleting it will end in tears.)
- Worked around a bug in macOS 11 (FB8925588) which created a bogus symlink to a nonexistent "BBEdit Backups" folder; when trying to save a document with "Keep historical backups" turned on, this resulted in an inappropriate prompt for sandbox access
- Fixed bug in which "Reload from Server" did not update the internal knowledge of the file's modification date on the server, such that a subsequent save would incorrectly report that the file on the server may have been modified
- Made a change to improve performance when dragging (or pasting the contents of) an extremely large file into an empty untitled document
- Made a change to reduce the amount of memory required when inserting a file's contents by dragging it into the text area in an editing window
- Fixed bug in which codeless language modules would fail to correctly generate folds in some cases, primarily when the closing block delimiter appeared at the very end of the file without a line break or whitespace after it
- BBEdit will forego live highlighting of selected text, as well as live highlighting of matches in the Find window, if the document is over 256MB in size. The limit is adjustable, but you rarely (if ever) should need to do so
The expert preference for changing the size limit is:
- defaults write com.barebones.bbedit LiveMatchSizeLimit -int N
- (N is an integer value, expressed in megabytes.)
- Fixed bug in which files requiring HTML conversion for deployment were skipped if all of the deployment preprocessing options (check syntax/links, update images/placeholders) were turned off
- Made a change which might prevent macOS from abnormally terminating the application during restart/shutown operations
- The HTML5 syntax checker will no longer report an error for the loading attribute in img and iframe elements, as long as the provided value is either lazy or eager
- When opening a file that is determined to be all ASCII characters, BBEdit uses the "Default text encoding for new documents" setting to choose the document's encoding, unless the setting is one of the UTF-16 values. If the setting has been changed to "Unicode (UTF-8, with BOM)", however, this has the unintended consequence of subsequently adding a UTF-8 BOM to the file when saving, which may be undesirable
- Therefore, if the default encoding setting is "Unicode (UTF-8, with BOM)" and BBEdit is opening an all-ASCII file, the document's encoding will be set to "Unicode (UTF-8)" (i.e. without a BOM) in order to preserve fidelity with the representation on disk
- Fixed bug in which using the "Restore Defaults" button in the Text Colors preferences did not reset the preferences UI to reflect the default state
- Fixed bug in which the window title bar icons of non-text documents (such as text factories) couldn't be dragged