Version 4.1.0 has been FINALIZED after additional testing and years of development. While 4.1.0 is out of beta, daily builds will switch to 5.0 alpha and remain potentially unstable.
This is the LAST VERSION TO SUPPORT MACOS VERSIONS 10.10 OR EARLIER. Version 5.0 alpha will likely require more recent versions of macOS.
New in 20180615:
Vector graphics windows once again support dragging a rectangle to zoom into a certain area (double-click to restore default zoom, and hit Escape to cancel a drag).
Vector graphics windows now support touch-based zooming, gradually zooming in or out as you use a track pad.
Vector graphics windows now use their zoomed size for Copy and Print (processing only a portion of the total image).
Vector graphics windows now have a margin area, similar to a terminal window; and, when a Format is applied, they use the Format’s matte background color. In addition, if the graphic is zoomed out very far, the matte color fills in the region outside the graphic.
Help has been updated to accurately describe all of the features of vector graphics windows.
New in 20180519:
Preferences window Full Screen pane has moved to Preferences window General pane Full Screen tab.
New in 20180322:
Terminal view information tags are now implemented as blue pop-overs with white text, instead of using "tooltips". (These appear during window resize. They also appear after an interrupt, suspend, vector graphics page, image file dump, or local echo of a control character.)
New in 20180317:
Fixed Preferences window General pane Notifications tab to correctly display the last saved bell setting instead of accidentally overwriting it with a default value.
New in 20180301:
Fixed window stacking to match top-left corner specified in Preferences instead of being slightly offset from it.
New in 20180212:
Fixed commands such as "Bring Next to Front", which could sometimes do nothing instead of selecting another window.
New in 20180105:
Terminals now support the DECRQSS sequence for DECSTBM (set top/bottom margins). This allows a program to determine the current scroll region.
The TELNET and regular FTP protocols are no longer supported in the graphical interface or in default URL handlers, since macOS High Sierra does not install the required tools. Secure shell (SSH) and secure FTP (SFTP) are still available. If you have a side installation of "telnet" or "ftp", you can use that by setting up a Session to run an appropriate command line. Also, you can use the MacTerm Quills interface in Python to define new URL handlers that run your side installations.
New in 20180101:
Terminals now support the DECRQSS sequence, though the response is initially "unrecognized value" for all inputs except DECSCUSR (cursor shape). This helps to avoid glitchy terminal output at startup in recent versions of "vim".
Terminals now support the DECSCUSR (set cursor shape) sequence from VT520, although the value is currently just stored for report requests (DECRQSS) without allowing applications to change the terminal cursor display. This helps to avoid glitchy terminal output at startup in recent versions of "vim".
XTerm terminals will now respond to VT220 Secondary Device Attributes queries by hijacking the 2nd return value for "XFree86 patch level", as XTerm does. The default value is 95, the minimum defined by XTerm. (Previously, the value 10 was returned, and terminals configured as only VT220 will continue to return 10.) This can encourage applications that read this value, such as text editors, to have better behavior; though it will always be difficult to predict exactly how this number will be used by any given application.
New low-level terminal preference "terminal-emulator-xterm-reported-patch-level" can be used to customize the "XFree86 patch level" returned in Secondary Device Attributes queries by terminals that use the XTerm emulator type. This is basically an XTerm hack but applications may depend on the specific value. This should be considered highly experimental and used only to encourage applications to produce desired behavior; since MacTerm may not perfectly emulate an XTerm, changing the patch level to arbitrary values may not do the correct thing.