Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sun, 10 Dec 2000 18:40:47 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [avail for test] readline-4.1-1 Message-ID: <20001210184046.A23227@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3A341632.11536.5F5B80D@localhost>; <20001210174902.B23010@redhat.com> <3A3421C0.21144.622DC01@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A3421C0.21144.622DC01@localhost>; from gerrit.haase@t-online.de on Mon, Dec 11, 2000 at 12:37:20AM +0100 On Mon, Dec 11, 2000 at 12:37:20AM +0100, Gerrit P. Haase wrote: ><10 Dec 2000, 17:49 Uhr wars, als Christopher Faylor folgendes schrub:> >< Re: [avail for test] readline-4.1-1 > > >> >Is it possible, that this behaviour was o.k. since last week? >> >> I don't know what shell you're talking about but bash does not use a DLL >> version of readline, so unless you built your own version of bash with >> this readline, any problems you are seeing are unrelated to this release. > >O.K., i got it, but what should i do now to get around this misbehaviour? I have no idea. Sorry. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com