Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
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: Paul Sokolovsky <paul-ml AT is DOT lg DOT ua>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Re[2]: Cursors do not work in bash under Win98
Date: Fri, 20 Aug 1999 20:39:59 GMT
Message-ID: <37bfbb95.11634239@mail.weiser.saale-net.de>
References: <37cc911a DOT 4784139 AT mail DOT weiser DOT saale-net DOT de> <1544 DOT 990820 AT is DOT lg DOT ua>
In-Reply-To: <1544.990820@is.lg.ua>
X-Mailer: Forte Agent 1.5/32.452
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello Paul, 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.
>[]
>MW> To Cygwin developers: Is this a known issue or should I compile some
>MW> information about it and send it to you?
>    It is known issue and really FAQ here. NEVER-EVER use m$
Oh, sorry, I didn't know that. I follow this list regularly and didn't
ever see something useful on that concern. I read the FAQ, searched
the list archives on every phrase that might mean cursor keys and just
completed another grep over my local archive. Can you please tell me
where I missed it?
-- 
bye, Michael

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com