[RFU] mintty-0.9b2-1
Please upload: wget http://mintty.googlecode.com/files/mintty-0.9b2-1.tar.bz2 wget http://mintty.googlecode.com/files/mintty-0.9b2-1-src.tar.bz2 wget http://mintty.googlecode.com/svn/tags/0.9-beta2/cygport/setup.hint This is another test release. 0.9b1-1 can be deleted. Thanks, Andy
Re: [RFU] mintty-0.9b2-1
On Sep 26 10:14, Andy Koppe wrote: Please upload: wget http://mintty.googlecode.com/files/mintty-0.9b2-1.tar.bz2 wget http://mintty.googlecode.com/files/mintty-0.9b2-1-src.tar.bz2 wget http://mintty.googlecode.com/svn/tags/0.9-beta2/cygport/setup.hint This is another test release. 0.9b1-1 can be deleted. Done. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: ITP: autobuild
On Sep 24 14:10, Charles Wilson wrote: On 9/20/2010 4:31 PM, Charles Wilson wrote: Yep, now we actually need votes. I have 4 votes, now; anybody want to spot me another? Chuck? Can you please update cygwin-pkg-maint as well? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
[RFU] lzip-1.11-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, http://spoon.yaxm.org/cygwin-1.7/lzip/setup.hint http://spoon.yaxm.org/cygwin-1.7/lzip/lzip-1.11-1.tar.bz2 http://spoon.yaxm.org/cygwin-1.7/lzip/lzip-1.11-1-src.tar.bz2 Please remove 1.9-1. Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (MingW32) iEYEARECAAYFAkyfZIQACgkQp56AKe10wHfkQQCfe2mmGi5CzpYgbk0U5eHi7/KB MNQAn1BUpqNxvMhgwCSEmibbVjIW69wg =eymy -END PGP SIGNATURE- 0xED74C077.asc Description: application/pgp-keys
Re: fvwm ignores clickToFocus for function keys
This conversation was transferred from the cygwin main list because Larry Hall said it was xfree-specific... From: Morgan Gangwere 0 dot fractalus at gmail dot com Sounds like something is trashing a buffer... however I'm not entirely sure. ... Sounds oddly configuration related... then again, i don't use fvwm on windows. My suspicion is that it has to do with the cut-buffers/clip-board-mechanism, somehow. I'd said previously that what gets sent (when a function key is pressed but the mouse cursor isn't over the in-focus window) is the unmapped version of the function key. It might also be some earlier contents of the cut-buffer, or something like that. I'm still trying to track it down. Being able to cut-and-paste between windows and cygwin is important, and I'm glad that this evolving capability is so far along... but is it possible to disable it, at least for debugging purposes? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: gvim tiny font in 1.7.7
Hi again, all -- ...and then David T-G said... % % Hi, all -- % ... % When I first started gvim after my install, the font was invisibly tiny % both for the content and for the menus. [Note that both xterm and rxvt-X [snip] Frederic asked if I had restarted my X server. I have logged out and in and even rebooted numerous times since installing but still have the same problem. TIA again HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt pgpBl87946LZ7.pgp Description: PGP signature
winsup/cygwin dcrt0.cc ChangeLog
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: c...@sourceware.org 2010-09-26 14:57:13 Modified files: cygwin : dcrt0.cc ChangeLog Log message: * dcrt0.cc (__main): Force signal synchronization. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/cygwin/dcrt0.cc.diff?cvsroot=uberbaumr1=1.386r2=1.387 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/cygwin/ChangeLog.diff?cvsroot=uberbaumr1=1.5057r2=1.5058
src/winsup/cygwin ChangeLog uinfo.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-09-26 15:45:11 Modified files: winsup/cygwin : ChangeLog uinfo.cc Log message: * uinfo.cc (cygheap_user::init): Call GetUserNameW and convert to multibyte here so as not to rely on the current ANSI page. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5058r2=1.5059 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/uinfo.cc.diff?cvsroot=srcr1=1.172r2=1.173
Re: cygwin : bash doesn't recognize BackSpace
Larry Hall (Cygwin reply-to-list-only-lh at cygwin.com writes: On 5/27/2010 10:11 AM, RISINGP1 at nationwide.com wrote: I was having trouble with the backspace key, but it was with pdksh, so I don't know if this will work for you, but it is worth a try... Andy Koppeandy.koppe at gmail.com wrote: From the cygwin-1.7.5 release announcement: - Support DEC Backarrow Key Mode escape sequences (ESC [ ? 67 h, ESC [ ? 67 l) in Windows console. (The first one switches to ^H. You'll need to set stty erase accordingly.) That's a different issue. The OP's problem is a conflict with MKS, particularly with environment variables both MKS and Cygwin use to define a working terminal setting. I have both MKS and cygwin. The following command: export TERM=cygwin fixed backspace issue. Before: $ env |grep TERM TERM=nutc TERMCAP=C:\PROGRA~1\MKSTOO~1\etc\termcap TERMINFO=C:\PROGRA~1\MKSTOO~1\usr\lib\terminfo After: $ env |grep TERM TERM=cygwin TERMCAP=C:\PROGRA~1\MKSTOO~1\etc\termcap TERMINFO=C:\PROGRA~1\MKSTOO~1\usr\lib\terminfo -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin slow on x64 systems
On Sun, Sep 26, 2010 at 12:54:58AM -0500, Yaakov (Cygwin/X) wrote: On Sun, 2010-09-19 at 20:36 -0400, Christopher Faylor wrote: On Sun, Sep 19, 2010 at 07:22:27PM -0500, Yaakov (Cygwin/X) wrote: cygserver starts but other services (messagebus, syslog-ng) do not with 20100919 snapshot. Ok, I'm back in WJFFM territory then. I can start sshd, cygserver, messagebus, and syslog-ng without problem. I've kept trying CVS HEAD with each revision, no change; other services fail with this Windows error? Error 1067: The process terminated unexpectedly. What further information can I provide? I just activated some code that I'd hoped was unnecessary. I'm building a new snapshot now. Could you try it when it shows up? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Testing: mintty-0.9b2-1
mintty 0.9b2-1 is on its way to the Cygwin mirrors. This is a test release.
To install it using setup.exe, find mintty on the package selection
screen and click on the cycle symbol by its version number until the
required version appears. Make sure the checkbox in the 'Bin?' column
next to it is ticked.
Alternatively, just click on the 'Exp' button at the top of the
package selection screen to install available test versions of all
installed packages, thereby helping to make sure they're stable.
Otherwise, a .zip can be downloaded from http://mintty.googlecode.com.
DESCRIPTION
===
Mintty is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
CHANGES
===
- Fixed crash in Ctrl+Tab handling that showed up on some setups.
- Handle VK_PACKET virtual key message, to ensure compatibility with
the AllChars utility for emulating a Compose key on Windows.
- Added automatic fallback scheme for VT100 line drawing characters.
If appropriate Unicode characters aren't available in the selected
font, ASCII approximations are used instead.
- Changed the SGR 21 sequence from setting the underline attribute to
selecting normal intensity, for compatibility with the Linux console.
(Xterm ignores this one.)
- Normalise incoming combining characters to the precomposed form, as
xterm does. This makes them look better on screen.
Previous changes compared to 0.8.3:
Display issues:
- On multimonitor systems, the window size is no longer limited to the
size of a single monitor.
- The program window should no longer be opened with parts off the
screen or obscured by the taskbar (unless of course the window is too
big too fit into the available workspace).
- Fixed an issue with cursor flicker on Vista and 7 with Aero disabled.
- The options dialog no longer flashes when changing page while
transparency is enabled, as happened on non-Aero systems.
Colours:
- Added ability to set the 16 ANSI colours in the config file (or on
the command line via the -o option), like so: 'Blue=0,0,255' or
'BoldGreen=128,255,128'. The manual has all the colour names.
- Added ability to switch cursor colour depending on whether the Input
Method Editor (IME) is active. This is activated by setting
'IMECursorColour' in the config file (or via the -o option). So, for
example, adding 'IMECursorColour=255,0,0' to ~/.minttyrc will turn the
cursor red when the IME is active. (IMEs allow entering characters
that aren't on the keyboard and are crucial for East Asian languages.)
- Renamed 'Show bold is bright' setting to 'Show bold as colour'.
- Removed the 'Use system colours instead' checkbox from the options
dialog. The 'UseSystemColours' config file setting remains.
Selection:
- Added config-file only 'WordChars' setting for controlling the
characters selected by a double click. By default, mintty uses an
algorithm that's geared towards picking out filenames and URLs. If
'WordChars' is set, that algorithm is disabled, and instead only
letters, digits, and the characters specified with this setting are
selected. For example, setting 'Wordchars=_' would ensure that C
identifiers are picked out correctly.
- Fixed a crash that occurred when copying lots of text on systems
with a doublebyte default codepage.
Xterm compatibility:
- Added support for xterm's VT220-style function key mode (as opposed
to the default PC-style keycodes), where Ctrl+F3 through Ctrl+F10
act as F13 through F20, the Home and End keys send different keycodes,
and the numpad sends application keypad codes if enabled with the
DECPAM sequence.
- In mouse tracking mode, concurrent mouse button presses are now
handled in the same way as they are in xterm, i.e. mintty no longer
sends a fake mouse release event when the second button is pressed.
- 'Extended Mouse Mode' as introduced in xterm #262 is now supported.
This allows row/column positions greater than 255 (and up to 2015) to
be reported, in case you do get that 30'' monitor ...
Misc:
- Alt+F4 prompts for exit confirmation if the shell has any child
processes, as already happens with the close button. (There's an
option for disabling this.)
- Added a tip to the manual on how to use Ctrl[+Shift]+Tab to switch
session in GNU screen.
QUESTIONS
=
The mintty manual is installed as a manpage ('man mintty'), and it's
also available in PDF format at
http://mintty.googlecode.com/files/mintty-0.9-beta2.pdf.
Questions and comments can be sent to the mintty discussion group at
http://groups.google.com/group/mintty-discuss or the Cygwin mailing
list. Please use the issue tracker at
http://code.google.com/p/mintty/issues/list to report bugs or suggest
enhancements.
To update your installation, click on the Install Cygwin now link
on the http://cygwin.com
Test installation of Sources Bugzilla upgraded to 3.6.2 available for testing
Hello everybody, Now that GCC Bugzilla has been successfully upgraded to version 3.6.2 last Thursday, it's now time to upgrade Sources Bugzilla (which is still running a version released in 2003!). I built a test installation available at: http://sourceware.org/bugzilla-test/ Please test it as much as possible, and report bugs before I upgrade the production installation. Please report bugs using this link: http://sourceware.org/bugzilla-test/enter_bug.cgi?product=Bugzilla Despite being a test installation, emails are sent for real, including to mailing-lists, so be careful when playing with it. ;) Assuming that no major bug is reported in the next few days, the upgrade will probably happen late this week, or early next week. You will be informed before the upgrade take place. Have fun testing the new Bugzilla! Frédéric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin slow on x64 systems
On Sun, 2010-09-26 at 10:58 -0400, Christopher Faylor wrote: On Sun, Sep 26, 2010 at 12:54:58AM -0500, Yaakov (Cygwin/X) wrote: I've kept trying CVS HEAD with each revision, no change; other services fail with this Windows error? Error 1067: The process terminated unexpectedly. What further information can I provide? I just activated some code that I'd hoped was unnecessary. I'm building a new snapshot now. Could you try it when it shows up? Services now run normally with the 20100926 snapshot. Thanks, Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin slow on x64 systems
On Sun, Sep 26, 2010 at 12:42:38PM -0500, Yaakov (Cygwin/X) wrote: On Sun, 2010-09-26 at 10:58 -0400, Christopher Faylor wrote: On Sun, Sep 26, 2010 at 12:54:58AM -0500, Yaakov (Cygwin/X) wrote: I've kept trying CVS HEAD with each revision, no change; other services fail with this Windows error? Error 1067: The process terminated unexpectedly. What further information can I provide? I just activated some code that I'd hoped was unnecessary. I'm building a new snapshot now. Could you try it when it shows up? Services now run normally with the 20100926 snapshot. Thanks, Sigh. Too bad. There's a noticeable slowdown from the additional code in that snapshot. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
setup.exe: How to install sources from the command line?
Hi, Google wasn't my friend here. I managed to install packages with the --category and --packages option of setup.exe. I didn't find out how to install sources. Thanks Al -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe: How to install sources from the command line?
2010/9/26 Al oss.el...@googlemail.com: Hi, Google wasn't my friend here. I managed to install packages with the --category and --packages option of setup.exe. I didn't find out how to install sources. There is a second cygwin setup skripting question. When I open the shell for the first time, the user directory is created. Is there a trigger to reach this without manually opening a login shell? I tried to open the shell from within a .bat script to trigger the user directory generation. P:\cygwin\bin\bash.exe - It blocked the batch script and took no additional --exec paramteter to exit on it's own. Al -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: My bash shell suddenly has X-ray vision
On 9/25/2010 9:27 PM, SJ Wright wrote: Or is it just the difference in encodings? In scripts and config/convenience files like .bashrc or .bash_aliases, it can see *through* crunches (#), which are supposed to make a line of text invisible to a shell or am I wrong on that? Could it be because I added a LANG variable and have been turning out not-quite-UTF-8 stuff from my one or two text editors? The only guess I can make with my limited knowledge is that, once UTF8 is set or enabled, ISO-8859-1 crunches, for all practical purposes, are meaningless to the shell. or am I wrong on that as well? A little help, please. This isn't making a whole lot of sense. What good are rules for comments if, when a new text encoding or environment variable is applied/undertaken/invoked, they become null and void? (Might as well go back to REM: from CLI BASIC.) I suggest you run 'd2u' on the files and see if that helps. If it does, you know that some editing you did on those files introduced DOS/Windows line endings. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin : bash doesn't recognize BackSpace
On 9/26/2010 9:30 AM, MikeS wrote: Larry Hall (Cygwinreply-to-list-only-lhat cygwin.com writes: On 5/27/2010 10:11 AM, RISINGP1at nationwide.com wrote: I was having trouble with the backspace key, but it was with pdksh, so I don't know if this will work for you, but it is worth a try... Andy Koppeandy.koppeat gmail.com wrote: From the cygwin-1.7.5 release announcement: - Support DEC Backarrow Key Mode escape sequences (ESC [ ? 67 h, ESC [ ? 67 l) in Windows console. (The first one switches to ^H. You'll need to set stty erase accordingly.) That's a different issue. The OP's problem is a conflict with MKS, particularly with environment variables both MKS and Cygwin use to define a working terminal setting. I have both MKS and cygwin. The following command: export TERM=cygwin fixed backspace issue. Before: $ env |grep TERM TERM=nutc TERMCAP=C:\PROGRA~1\MKSTOO~1\etc\termcap TERMINFO=C:\PROGRA~1\MKSTOO~1\usr\lib\terminfo After: $ env |grep TERM TERM=cygwin TERMCAP=C:\PROGRA~1\MKSTOO~1\etc\termcap TERMINFO=C:\PROGRA~1\MKSTOO~1\usr\lib\terminfo Right. Cygwin doesn't understand nutc as a terminal type (just as MKS doesn't know cygwin). Setting the terminal type correctly for Cygwin makes all the difference. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup.exe: How to install sources from the command line?
On 9/26/2010 5:56 PM, Al wrote: When I open the shell for the first time, the user directory is created. Is there a trigger to reach this without manually opening a login shell? The check is in '/etc/profile'. It's just checking if $HOME exists. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: My bash shell suddenly has X-ray vision
Larry Hall (Cygwin) wrote: On 9/25/2010 9:27 PM, SJ Wright wrote: Or is it just the difference in encodings? In scripts and config/convenience files like .bashrc or .bash_aliases, it can see *through* crunches (#), which are supposed to make a line of text invisible to a shell or am I wrong on that? Could it be because I added a LANG variable and have been turning out not-quite-UTF-8 stuff from my one or two text editors? The only guess I can make with my limited knowledge is that, once UTF8 is set or enabled, ISO-8859-1 crunches, for all practical purposes, are meaningless to the shell. or am I wrong on that as well? A little help, please. This isn't making a whole lot of sense. What good are rules for comments if, when a new text encoding or environment variable is applied/undertaken/invoked, they become null and void? (Might as well go back to REM: from CLI BASIC.) I suggest you run 'd2u' on the files and see if that helps. If it does, you know that some editing you did on those files introduced DOS/Windows line endings. I did something slightly different, inspired by your suggestion. I wrote up a quickie script to get the magic number returns from 'find' on all my dotfiles. This after running several different combinations of 'cat' with options. Re ALL the files in question: there were *NO* ^M markers at the end of any line. I regard running dos2unix a waste of time if I don't see some indication of non-Unix encoding/formatting on a file or files ahead of time. And I may not know much but I know what to look for. Or maybe you'd prefer to take up the subject of what saves which correctly with the developers of Emerald Editor, which I use both in Windows and Ubu Linux to compose scripts and edit dotfiles regularly when I'm not in the mood for the mouseless approach vi and nano restrict one to. A solution that's not a solution isn't even worth considering (was that Einstein or Schrodinger? Maybe it was Dr Moore.) steve w Attached is the output to text of that script (which returned as *magic_returns_dotfiles.txt: ASCII text* one-half second ago). ~/.Xauthority: empty ~/.Xdefaults: ASCII text ~/.Xresources: Little-endian UTF-16 Unicode text, with CRLF line terminators ~/.bash_aliases: ASCII English text ~/.bash_history: ASCII English text ~/.bash_profile: ASCII English text ~/.bashrc: ASCII English text ~/.blackboxrc: ASCII text ~/.curlrc: ASCII text ~/.gtk-bookmarks: ASCII text ~/.imrc: ASCII text ~/.inputrc: ASCII English text ~/.jwmrc: XML document text ~/.minttyrc: ASCII text ~/.profile: ASCII English text ~/.wmcliphistrc: empty ~/.xinitrc: POSIX shell script text executable ~/.xserverrc: POSIX shell script text executable ~/.xsession: ASCII English text -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: My bash shell suddenly has X-ray vision
On 27 September 2010 04:27, SJ Wright wrote: Or is it just the difference in encodings? In scripts and config/convenience files like .bashrc or .bash_aliases, it can see *through* crunches (#), which are supposed to make a line of text invisible to a shell or am I wrong on that? Could it be because I added a LANG variable and have been turning out not-quite-UTF-8 stuff from my one or two text editors? The only guess I can make with my limited knowledge is that, once UTF8 is set or enabled, ISO-8859-1 crunches, for all practical purposes, are meaningless to the shell. To answer that part: no, UTF-8 vs ISO-8859-1 makes no difference to that symbol, because it's part of the ASCII range, which is shared between all of the character encodings supported by Cygwin. the mouseless approach vi and nano restrict one to. They do you have some mouse support actually. Enable with ':set mouse=a' in vim, and with Alt+m in nano. ~/.Xresources: Little-endian UTF-16 Unicode text, with CRLF line terminators That one won't work, because UTF-16 is not ASCII-compatible. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Testing: mintty-0.9b2-1
mintty 0.9b2-1 is on its way to the Cygwin mirrors. This is a test release.
To install it using setup.exe, find mintty on the package selection
screen and click on the cycle symbol by its version number until the
required version appears. Make sure the checkbox in the 'Bin?' column
next to it is ticked.
Alternatively, just click on the 'Exp' button at the top of the
package selection screen to install available test versions of all
installed packages, thereby helping to make sure they're stable.
Otherwise, a .zip can be downloaded from http://mintty.googlecode.com.
DESCRIPTION
===
Mintty is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
CHANGES
===
- Fixed crash in Ctrl+Tab handling that showed up on some setups.
- Handle VK_PACKET virtual key message, to ensure compatibility with
the AllChars utility for emulating a Compose key on Windows.
- Added automatic fallback scheme for VT100 line drawing characters.
If appropriate Unicode characters aren't available in the selected
font, ASCII approximations are used instead.
- Changed the SGR 21 sequence from setting the underline attribute to
selecting normal intensity, for compatibility with the Linux console.
(Xterm ignores this one.)
- Normalise incoming combining characters to the precomposed form, as
xterm does. This makes them look better on screen.
Previous changes compared to 0.8.3:
Display issues:
- On multimonitor systems, the window size is no longer limited to the
size of a single monitor.
- The program window should no longer be opened with parts off the
screen or obscured by the taskbar (unless of course the window is too
big too fit into the available workspace).
- Fixed an issue with cursor flicker on Vista and 7 with Aero disabled.
- The options dialog no longer flashes when changing page while
transparency is enabled, as happened on non-Aero systems.
Colours:
- Added ability to set the 16 ANSI colours in the config file (or on
the command line via the -o option), like so: 'Blue=0,0,255' or
'BoldGreen=128,255,128'. The manual has all the colour names.
- Added ability to switch cursor colour depending on whether the Input
Method Editor (IME) is active. This is activated by setting
'IMECursorColour' in the config file (or via the -o option). So, for
example, adding 'IMECursorColour=255,0,0' to ~/.minttyrc will turn the
cursor red when the IME is active. (IMEs allow entering characters
that aren't on the keyboard and are crucial for East Asian languages.)
- Renamed 'Show bold is bright' setting to 'Show bold as colour'.
- Removed the 'Use system colours instead' checkbox from the options
dialog. The 'UseSystemColours' config file setting remains.
Selection:
- Added config-file only 'WordChars' setting for controlling the
characters selected by a double click. By default, mintty uses an
algorithm that's geared towards picking out filenames and URLs. If
'WordChars' is set, that algorithm is disabled, and instead only
letters, digits, and the characters specified with this setting are
selected. For example, setting 'Wordchars=_' would ensure that C
identifiers are picked out correctly.
- Fixed a crash that occurred when copying lots of text on systems
with a doublebyte default codepage.
Xterm compatibility:
- Added support for xterm's VT220-style function key mode (as opposed
to the default PC-style keycodes), where Ctrl+F3 through Ctrl+F10
act as F13 through F20, the Home and End keys send different keycodes,
and the numpad sends application keypad codes if enabled with the
DECPAM sequence.
- In mouse tracking mode, concurrent mouse button presses are now
handled in the same way as they are in xterm, i.e. mintty no longer
sends a fake mouse release event when the second button is pressed.
- 'Extended Mouse Mode' as introduced in xterm #262 is now supported.
This allows row/column positions greater than 255 (and up to 2015) to
be reported, in case you do get that 30'' monitor ...
Misc:
- Alt+F4 prompts for exit confirmation if the shell has any child
processes, as already happens with the close button. (There's an
option for disabling this.)
- Added a tip to the manual on how to use Ctrl[+Shift]+Tab to switch
session in GNU screen.
QUESTIONS
=
The mintty manual is installed as a manpage ('man mintty'), and it's
also available in PDF format at
http://mintty.googlecode.com/files/mintty-0.9-beta2.pdf.
Questions and comments can be sent to the mintty discussion group at
http://groups.google.com/group/mintty-discuss or the Cygwin mailing
list. Please use the issue tracker at
http://code.google.com/p/mintty/issues/list to report bugs or suggest
enhancements.
To update your installation, click on the Install Cygwin now link
on the http://cygwin.com
