public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Small request for the new cygwin terminal
Date: Thu, 07 Jun 2012 18:45:00 -0000	[thread overview]
Message-ID: <CAHWeT-Z+LG94LO4v2UVCWDiQ87CSVf4sgC7GcWzzWnQk-OR77w@mail.gmail.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A70C799@USA7109MB022.na.xerox.net>

On 7 June 2012 15:56, Nellis, Kenneth wrote:
> -----Original Message-----
> From: Andy Koppe
> <snip/>
> It is done on purpose, to allow Shift+Esc to be bound to a different
> function if desired. It's documented here:
>
> [1] http://code.google.com/p/mintty/wiki/Keycodes#Special_keys
>
> Shift+ESC sends the Unicode codepoint U+009B, aka the Control Sequence
> Introducer (CSI) character.
> <snip/>
> -----END Original Message-----
>
> My experience does not agree with the "Special keys" table at the
> page referenced by that URL.
>
> When pressing the unmodified Pause/Break key, I get ^], which maps
> to Pause in your table, and pressing Ctrl+Pause/Break, I get ^\,
> which maps to Break in your table, so this agrees with the statement,
> "Pause and Break usually share a key, whereby Ctrl has to be pressed
> to get the Break function."
>
> But, when I press Shift+Pause/Break, because I'm not pressing Ctrl,
> I should get your table's Pause/Shift result, U+009C, but I get 9D.
> Similarly, when I press Ctrl+Shift+Pause/Break, because I am pressing
> Ctrl, I should get your table's Break/Shift result, U+009D, but I get 9C.

Oops, documentation error. Now fixed. Thanks very much for testing that.

The intention is that the Shift combination sends the basic control
character plus 0x80. See also the preceding section (which I've now
added a link to from the Special Keys section):

http://code.google.com/p/mintty/wiki/Keycodes#Ctrl

> Also, when I press either Ctrl+Tab or Ctrl+Shift+Tab, instead of
> getting what the table indicates, I don't get anything at all.

You've probably got the shortcuts for switching among mintty windows
enabled on the Keys page of the options.

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

  parent reply	other threads:[~2012-06-07 18:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  8:41 Lluís Batlle i Rossell
2012-06-07 11:22 ` Andy Koppe
2012-06-07 14:59   ` Nellis, Kenneth
2012-06-07 15:52     ` Helmut Karlowski
2012-06-07 16:10       ` Helmut Karlowski
2012-06-07 19:12         ` Andy Koppe
2012-06-07 20:13           ` Helmut Karlowski
2012-06-08  3:57             ` Andy Koppe
2012-06-07 18:45     ` Andy Koppe [this message]
2012-06-08 18:02       ` Nellis, Kenneth
2012-06-08 19:18         ` Andy Koppe
2012-06-11 12:55           ` Nellis, Kenneth
2012-06-11 20:07             ` Helmut Karlowski
2012-06-12  4:23               ` Andy Koppe
2012-06-12  4:21             ` Andy Koppe
2012-06-12 13:11               ` Nellis, Kenneth
2012-06-15 12:16                 ` Andy Koppe
2012-06-08 12:54 Helmut Karlowski
2012-06-08 19:14 ` Andy Koppe

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=CAHWeT-Z+LG94LO4v2UVCWDiQ87CSVf4sgC7GcWzzWnQk-OR77w@mail.gmail.com \
    --to=andy.koppe@gmail.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).