Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: michael AT weiser DOT saale-net DOT de (Michael Weiser) To: Nuno Bandeira Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Cursors do not work in bash under Win98 Date: Thu, 19 Aug 1999 23:23:36 GMT Message-ID: <37cc911a.4784139@mail.weiser.saale-net.de> References: <37BB7AF0 DOT 663A432B AT di DOT fct DOT unl DOT pt> In-Reply-To: <37BB7AF0.663A432B@di.fct.unl.pt> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Nuno, you wrote: > What happens is that whenever I run bash using the standard supplied cygnus >icon, everything works just fine (environment, bashrc, HOME) except the cursor >keys... I can't edit my command line neither browse through bash's history. A friend of mine had the same problem with his German Win98 and after a lot of searching in the mailing list archives, creative guessing and just trying all weird keys I ever thought of I figured out, that at least for him it works when he enables Num-Lock and uses the cursor key representations on the numeric key block instead. To Cygwin developers: Is this a known issue or should I compile some information about it and send it to you? -- bye, Michael -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com