SUPPORT : TextWrangler : Archived Release Notes : TextWrangler 1.5 Release Notes
TextWrangler 1.5 Release Notes
This page documents all feature enhancements and bug fixes included in the TextWrangler 1.5 release. For complete details on previous releases, please see the release notes archive.
For information on using TextWrangler, please refer to the online Help, or the PDF user manual (available by selecting "TextWrangler Manual" from the Help menu).
Additions
The following features and enhancements are new for TextWrangler 1.5:
-
TextWrangler 1.5 requires Mac OS X 10.2 or later (10.2.6 or later strongly recommended).
-
TextWrangler now offers extensive AppleScript support: it is scriptable, recordable, and attachable. It employs the object model text suite, which enables access to window contents in terms of characters, words, and lines.
Like Mailsmith, TextWrangler also supports a subset of the BBEdit scripting suite for access to the powerful text manipulation features which are common to both BBEdit and TextWrangler. Plug-ins may also be scripted, if the plug-in developer has made them so. (Some of the factory plug-ins supplied with TextWrangler are scriptable.)
Use the "Open Scripting Dictionary" command on the Script menu to view TextWrangler's scripting terminology.
-
TextWrangler adds built-in support for syntax coloring and function navigation of source files written in the following languages: Fortran, Java, Object Pascal, Perl, Python, Rez, Tcl, TeX, Unix shell script
-
Includes the "Configure TeX Coloring" plug-in to allow configuration of math-mode string coloring in TeX source files.
Fixes
The following problems have been corrected in TextWrangler 1.5:
-
Made a change to improve drawing (and scrolling) performance in syntax-colored documents with long runs of non-colored text (such as HTML documents).
-
Fixed bug in which using commands on the Font menu would fail if the text view of a browser window (disk browser, search results) was active.
-
Fixed bug in which Grep patterns weren't colored in the Find dialog.
-
TextWrangler 1.0 enforced a limitation that you could not compare a Unicode file against a non-Unicode file. This tended to pose a problem, since single-byte files in encodings other than Mac Roman are now represented internally as Unicode in situations where they weren't before, and so attempts to compare them to Mac Roman files would fail without visible explanation. Beginning with this version, no restriction is imposed on comparing two files with differing states of Unicode-ness.
-
When opening an encoded (i.e. non-Mac Roman, non-Unicode) text file, the file is now always represented as Unicode internally, and no attempt is made to guess the file's display script unless absolutely necessary. This improves the performance of opening large encoded files, and also resolves the observed behavior in which some Web pages which contained characters not existing in ISO-Latin-1 would open up with a Korean display font.
-
TextWrangler now accepts typeless text files dragged on to the Find Differences dialog.
-
When doing an Open Selection in an untitled editing window (or other window in which there's no file system context), TextWrangler will now look for an open document with the appropriate name before searching the file system.
-
Corrected a bug where adjusting the tab width in a document wrapped by character width didn't cause the text to be reflowed.
-
The behavior of forward delete and Clear are now consistent with respect to delete and the dirty status of empty untitled windows.
-
Fixed a bug in the save options dialog where the initial value for the state popup was incorrect.
-
When processing an entire file, the progress bar for Process Lines Containing was incorrect.
-
Fixed a bug where if the application was in the background when a plug-in finished execution, and that plug-in didn't have the dialog savvy bit turned on, the menu bar would be disabled.
-
Corrected a bug where multi-file search didn't find non-ASCII characters correctly in encoded text files.
-
Corrected a bug where non-ASCII characters were displayed incorrectly in search results list for encoded text files.
-
Non-breaking spaces are treated just like all other non-ASCII characters by the syntax checker with respect to entity encoding.
-
Corrected a bug where grep substition of "\\1" didn't work if you left out the Unicode parameter and the last search was on Unicode data.
(This overloading was unintentional anyway - the Unicode parameter specifies whether you want the result returned in Unicode, and this is now controllable seperately. The user doesn't know if we represented something internally as Unicode, and now doesn't have to.)
In addition, rather than the default for Unicode always being false, it is now computed based on the last data searched.
-
Corrected a bug in the undo to clean log where if you opened a saved document, typed something, undo the document would not be marked clean.
-
Fixed a bug where some custom keybindings could be lost across an Open/Save dialog invocation; this includes modifications to the Edit menu keybindings, as well as the "Hide TextWrangler" command.
-
If you have custom Edit menu bindings that don't include the Command key, they now work in dialogs.
-
The Paste menu item is correctly enabled when an Open/Save dialog is up.
-
Copy Path in the Info dialog canonically composes the Unicode before placing it on the clipboard (like copy path from the status bar does).
-
Dragging a file path into a window with a Unicode backing store inserts canonically composed Unicode.
-
Fixed bug in which files inserted using the "Insert File Contents" command were inserted in whatever order the OS provided them, which was not necessarily alphabetical. They are now sorted by name.
-
Fixed incorrect file-reading behavior which would occur when the default text-encoding preference was set to a Unicode encoding; the "Read As" option in the Open dialog would be ignored, as would any meta-information in the file itself (charset tag or saved state).
-
Fixed bug which would cause creation of documents with an initial "text encoding" property to fail. Scripts of this form should now work:
Make new text document with properties {encoding:"windows-1252"}
-
Changed the mechanics of how the application remembers recent files, so as to avoid hangs on Mac OS X caused by an OS bug.
-
The "Read As" option in the Open dialog now absolutely overrides the file's saved state; thus, it functions as a true override, rather than a modified auto-detect and is more useful.
-
When performing a multi-file Replace All, the application will now preflight the file save and log an error if the file about to be saved contains characters that can't be represented in the file's encoding, rather than writing those characters out as 0x1A in the file.
-
When performing a multi-file Replace All, if an error occurs while trying to save the changed file, the application will now leave the file open.
-
Worked around OS performance problem which would cause the SPOD to appear after putting a large styled-text item on the Clipboard in another application (e.g. TextEdit).
-
The application now no longer notifies the Finder when a document is saved or closed. (There was no particular reason for it to do so, since the Finder doesn't care.) This works around a bug in the Finder in which the Finder would hang, which would in turn cause the application to stall until the Apple Event notification timed out (which would take a couple of minutes per file).