X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.1 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: References: <0D835E9B9CD07F40A48423F80D3B5A70C799 AT USA7109MB022 DOT na DOT xerox DOT net> Date: Fri, 8 Jun 2012 04:57:26 +0100 Message-ID: Subject: Re: Small request for the new cygwin terminal From: Andy Koppe 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: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 7 June 2012 21:14, Helmut Karlowski wrote: > 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 don't think you can have different terminfo entries for different character sets for the same terminal type, i.e. you'd need to create charset-specifc types such as "xterm-cp850". > 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, nor why the xterm terminfo for it is empty. > I'm not sure if this can be solved inside mintty, is > there a fallback if an entry in terminfo is missing? There isn't a fallback in the terminfo system itself, so I guess that's up to each terminfo-using program (or its configuration). 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