public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Helmut Karlowski" <helmut.karlowski@ish.de>
To: cygwin@cygwin.com
Subject: Re: Small request for the new cygwin terminal
Date: Thu, 07 Jun 2012 20:13:00 -0000	[thread overview]
Message-ID: <op.wfjuigm7ofd6j1@nebbiolo> (raw)
In-Reply-To: <CAHWeT-aS7QVDCjBMqUtn=B3zpRzqY9u7m6WuG56ZFqQ=wy4Erw@mail.gmail.com>

Andy Koppe, 07.06.2012 21:12:05:

> CP850 doesn't support the C1 control characters, so you get the
> fallback instead, which is the scheme for encoding the Meta modifier
> when bit 7 isn't available. This means that Ctrl+Shift+letter
> combinations can't be distinguished from Ctrl+Alt+letter, but since
> Ctrl+Alt+letter combinations are suppposedly reserved for global
> shortcuts in Windows, they might still come in handy occasionally.
>
> There indeed is another scheme of encoding C1 control characters with
> an ESC followed by the base character, e.g. ^[A instead of ^[^A, but
> that would have made the Ctrl+Shift+letter keycode the same as
> Alt+letter rather than Ctrl+Alt+letter, which is why I chose the Meta
> scheme.
>
> I hope that makes some sense.

Yes. One question remains: Does the Character Set (ISO, CP, etc.) have an  
effect on the terminfo-terminal-description? I've added

csin=\233,

but I'm not sure if it's really necessary, and if it's wrong when I switch  
the Character Set. tgetstr() returns the value defined in xterm-terminfo,  
which may be wrong for another character set. When csin is missing in  
xterm, tgetstr() returns 0. I'm not sure if this can be solved inside  
mintty, is there a fallback if an entry in terminfo is missing?

-- 
Helmut Karlowski

--
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

  reply	other threads:[~2012-06-07 20:13 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 [this message]
2012-06-08  3:57             ` Andy Koppe
2012-06-07 18:45     ` Andy Koppe
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=op.wfjuigm7ofd6j1@nebbiolo \
    --to=helmut.karlowski@ish.de \
    --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).