Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Envelope-Sender-Is:	Andrej DOT Borsenkow AT mow DOT siemens DOT ru (at relayer david.siemens.de)
From:	"Andrej Borsenkow" <Andrej DOT Borsenkow AT mow DOT siemens DOT ru>
To:	"Uther Pendragon" <uther AT uth3r DOT dhs DOT org>, "Egor Duda" <cygwin AT cygwin DOT com>
Cc:	"Cygwin Mailing List" <Cygwin AT Sourceware DOT Cygnus DOT Com>
Subject:	RE: Cygwin Termcap information involving extended ascii charicters
Date:	Mon, 26 Feb 2001 11:58:13 +0300
Message-ID:	<002901c09fd2$400bfd50$21c9ca95@mow.siemens.ru>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To:	<82238417726.20010226114504@logos-m.ru>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Importance:	Normal

>
> Box  characters have nothing to do with extended ascii codes. They are
> described in acsc capability in your terminfo entry. Your problem with
> mc  arise from the fact that windows consoles have 2 modes -- ansi and
> oem.   Original  terminfo  entry  was  written for oem mode, which was
> default  at that time. Sometime ago cygwin have changed its default to
> ansi   mode and it lead to problem with box characters -- in ansi mode
> box   characters  have different codes.
>
> To  solve  your  problem  you  have  two   options. You can either set
> cygwin default console mode to 'oem' by  adding    'codepage:oem'   to
> your CYGWIN variable, or change acsc capability in terminfo entry.
>

Unix that I'm working on has two console terminfo's, at386 and at386-iso,
corresponding to OEM and ANSI cases. Cygwin could take the same way and set
TERM to two different strings depending on codepage value.

In cany case, if ANSI is now default, default termcap/terminfo should
obviously corespond to this.

-andrej


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -