mintty 0.5-beta2 is available for download from http://mintty.googlecode.com.
That's right, "mintty" rather than "MinTTY", because I got a bit tired
of the slightly silly capitalisation, which didn't really suit a
program that's meant to be simple and minimalist.
This release restores compatibility with Cygwin 1.5. There are
separate binaries for 1.5 and 1.7, so make sure you pick the right
one. The 1.7 version will not work on 1.5.
The 1.5 version will work on both 1.5 and 1.7, but has some
limitations regarding charset support. It also continues to flash up a
subliminal console when starting on Window 7, whereas that's gone with
the 1.7 version.
Other changes since beta1:
- mintty should now run on NT4, although with some limitations due to
lack of features such as window transparency. I haven't been able to
test this though, so any feedback would be welcome. (Speaking of
which, is anyone here running mintty on Windows 2000? Any problems?)
- Simplified configuration of the terminal bell. It's now possible to
have it flash the screen and play the system sound at the same time,
if that's what you want. They're both off by default. Also, the option
for continuous flashing of the taskbar is gone, so only the former
"Steady" mode is available now. (The taskbar highlighting only happens
if the bell is rung without the mintty window being active.)
- Restored backward compatibility with pre-0.5 "Codepage" setting.
- Changed behaviour of locale/charset settings again. The charset
field no longer is disabled if no locale is set. If a charset is
picked in that case, the Windows user locale (from the Region&Language
control panel) is filled in automatically.
Previous changes from 0.4.4:
- Added an option to enable the command line scrollback when on the
alternate screen (used by fullscreen apps such as editors). This
option is off by default, in which case the mousewheel now
sends standard cursor keycodes when on the alternate screen. Hence,
mousewheel scrolling in 'less' should now work without special
- The mintty-0.4 mousewheel keycodes can be enabled and disabled using
the new control sequences "\e[?7787h" and "\e[?7787l". These can be
used to distinguish the mousewheel from the cursor keys without
enabling full mouse reporting.
- The default backspace keycode now is ^? rather than ^H, to make Ctrl
+H available as a shortcut for other purposes, particularly help in
emacs. The backspace keycode option is gone. Instead, the DECBKM
control sequence is now supported.
- The (slightly mysterious) escape keycode option was replaced with a
mintty-specific control sequence: \e[?7728h to switch to ^\, and \e[?
7728l for standard ^[.
- Added 'Ctrl+Alt is AltGr' option. This is on by default, for
standard Windows behaviour. If switched off, Ctrl+LeftAlt is treated
separately from AltGr.
Locales and charsets:
- The 'Codepage' option is now called 'Character set', and there's a
new 'Locale' option for language and territory.
- If no locale is set in the options, mintty uses the locale specified
via the environment variables LC_ALL, LC_CTYPE, or LANG.
- If the locale option is set, the character set is appended to it and
the LANG variable set accordingly. LC_ALL and LC_CTYPE are cleared.
The @cjknarrow locale modifier is automatically appended to LANG if an
ambiguous-narrow font is used with an East Asian locale. (See also
- Any character sets supported by Cygwin or Windows can be used. The
dropdown menu lists many of those supported by Cygwin, including UTF-8
and the ISO-8859 character sets. Windows codepage can be entered
manually using the CP123 format. (Just entering the number works too.)
- East Asian double-byte character sets such as GBK and eucJP are now
- Unicode characters outside the basic multilingual plane can now be
displayed, assuming a suitable font is available, which should always
be the case on Vista and 7. (Please note, however, that currently
many programs do not support these correctly, due to Windows' use of
UTF-16 to represent Unicode).
- Removed "SCOANSI" control sequences, which were already disabled by
- Rearranged options dialog.
The manual page still needs to be brought up-to-date with these
As always, keep your questions, bug reports and enhancements requests