Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Sun, 19 Nov 2000 15:00:04 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: OemToAnsi patch from 2000-07-04 Message-ID: <20001119150004.A11587@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <1091101003 DOT 20001115120228 AT logos-m DOT ru> <20001115105258 DOT A7529 AT redhat DOT com> <20001115174147 DOT A20315 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from fujieda@jaist.ac.jp on Mon, Nov 20, 2000 at 04:56:49AM +0900 On Mon, Nov 20, 2000 at 04:56:49AM +0900, Kazuhiro Fujieda wrote: >>>> On Wed, 15 Nov 2000 17:41:47 -0500 >>>> Christopher Faylor said: > >> >http://sources.redhat.com/ml/cygwin/2000-10/msg00848.html >> >> Has anyone else actually tried this patch? I have grown leery of >> applying patches that "work fine" in the console code. > >I tried it. His code for emulating various terminal capabilities >didn't work fine to me. Once CYGWIN=codepage:oem is supported, >there isn't much need of the code switching ANSI/OEM codepages. I'm not sure about this. It might be nice to switch back and forth in a single message. >> If this is desirable, I'll look into getting an assignment and >> applying the patch. > >So it isn't always desirable. Thanks for trying this. It seems to be a universal rule that when someone touches this part of the console code they always break something. :-) cgf