Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Sun, 22 Aug 1999 13:37:11 -0400 From: Chris Faylor To: Nuno Bandeira Cc: Paul Sokolovsky , cygwin@sourceware.cygnus.com Subject: Re: Cursors do not work in bash under Win98 Message-ID: <19990822133711.C957@cygnus.com> Reply-To: cgywin@sourceware.cygnus.com Mail-Followup-To: Nuno Bandeira , Paul Sokolovsky , cygwin@sourceware.cygnus.com References: <37BEE03D.937393EF@di.fct.unl.pt> <5906.990821@is.lg.ua> <37C018A5.2574DC29@di.fct.unl.pt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37C018A5.2574DC29@di.fct.unl.pt>; from Nuno Bandeira on Sun, Aug 22, 1999 at 04:35:01PM +0100 On Sun, Aug 22, 1999 at 04:35:01PM +0100, Nuno Bandeira wrote: > Ahhhh, you meant Windows keyb in autoexec.bat! That thought would never >cross my mind because everything works just fine in every Win98/command.com >application. My problem is specifically with the default cygwin bash window, >so I don't think I'll be messing around with my Windows config for what is >probably a known problem. My impression was that people had found ways to fix this problem. The Cygwin code uses standard Win32 API calls to get it's keystrokes. I have no idea why there would be problems with arrow keys and I'm not going to be much help debugging the problem. This will require a cygwin developer (Sergey or Corinna perhaps) who use a non-US keyboard to isolate and fix the problem, if there is a problem. -chris -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com