X-Spam-Check-By: sourceware.org Message-ID: Date: Fri, 5 May 2006 14:10:54 -0400 From: "Jeff Lange" To: cygwin AT cygwin DOT com Subject: Re: terminal escape codes In-Reply-To: <445B9333.6090109@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Disposition: inline References: <445B9333 DOT 6090109 AT cygwin DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k45IB10E018719 While that does work, It unfortunately isn't an acceptable solution for me. I really need to be running this from a plain text console. Any other ideas? Thanks. -Jeff On 5/5/06, Larry Hall (Cygwin) wrote: > Jeff Lange wrote: > > Hi, > > I have a program that will connect to another host via telnet and > > work like a terminal emulator. This works fine in Linux, but under > > cygwin, when the host sends out the vt220 command (B cygwin > > apparently doesn't know how to handle this escape code, and it ends up > > displaying the B on the screen, > > > > In Linux if I type "echo ^[(Btest" at a command prompt it comes back > > as "test", but if I do the exact same thing at a cygwin prompt it > > comes back as "Btest" > > > > Does anyone know a simple way around this? > > > Run rxvt (or xterm if you're running X) instead? > > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 838 Washington Street (508) 893-9889 - FAX > Holliston, MA 01746 > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/