X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-5.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <877464.991851838-sendEmail@nebbiolo>
References: <877464 DOT 991851838-sendEmail AT nebbiolo>
Date: Fri, 8 Jun 2012 20:14:22 +0100
Message-ID: <CAHWeT-a9PVbU1eMHzuSXEf0nWu_5GcJz3yqaBSh8SQzeFcGQpQ@mail.gmail.com>
Subject: Re: Small request for the new cygwin terminal
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 8 June 2012 13:55, Helmut Karlowski wrote:
>
> Andy Koppe wrote:
>> > 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.
>>
>> Looking at the standard, 'csin' isn't meant for a keycode, but for a
>> command sent to the terminal, namely for the Init sequence for
>> multiple codesets. I'm afraid I don't know what that means though,
>
> That was the closest I've found in the terminfo-manpage. What is the
> terminfo-code for CSI (if any)?

I don't know of one, and I'm not sure it's necessary, since CSI is a
well-defined control character.

> How does vi know about CSI and its
> sequence as mentioned in your previous post?

It's hardcoded to U+009B (decimal 155) in vim:

http://vimdoc.sourceforge.net/htmldoc/intro.html#%3CCSI%3E

And since it works in both UTF-8 and ISO-8859-x, it would appear that
vim does the charset decoding before matching mappings, which is
great.

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