From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: mintty and modifier keys
Date: Thu, 19 Jul 2012 17:20:00 -0000 [thread overview]
Message-ID: <20120719172030.GC24611@ednor.casa.cgf.cx> (raw)
In-Reply-To: <BLU0-SMTP4411C7CA9BD02DF61D792E1CED90@phx.gbl>
On Thu, Jul 19, 2012 at 06:56:39PM +0200, Aaron Schneider wrote:
>On 19/07/2012 17:37, Ryan Johnson wrote:
>> Hi all (mostly Andy),
>>
>> I notice that mintty 1.1 handles certain key combinations differently
>> than xterm:
>
>Could you report it to the mintty developer?
>http://code.google.com/p/mintty/
I'm pretty sure the developer reads this mailing list.
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
next prev parent reply other threads:[~2012-07-19 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 15:38 Ryan Johnson
2012-07-19 16:56 ` Aaron Schneider
2012-07-19 17:20 ` Christopher Faylor [this message]
2012-07-19 19:06 ` Andy Koppe
2012-07-19 20:32 ` Ryan Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120719172030.GC24611@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).