X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Message-ID: <4A67102C.2010101@byu.net> Date: Wed, 22 Jul 2009 07:12:12 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Readline not working anymore in interactive interpreters References: <4A670358 DOT 8060504 AT byu DOT net> <4A670891 DOT 10209 AT byu DOT net> <4A670A97 DOT 1030800 AT byu DOT net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Olivier Lefevre on 7/22/2009 7:01 AM: > I was hoping we would not be playing ye olde finger-pointing > game. It used to work and it no longer does yet the interpreter > has not changed. How could it not be an issue within Cygwin? But your question is how readline is not working, and yet your cygcheck shows that q is not even using readline (unless it is loading it dynamically after the fact, as if by dlsym). So you're probably asking the wrong question. About the only other idea I have is that your terminal is behaving differently than it used to, but it doesn't look like you are using mintty, which was the only other recently updated cygwin package in 1.5 that seems like it would be relevant. Or maybe you changed your environment variables, such that cygwin is now passing a tty (which q sees as a pipe) instead of a console. But since the cygwin 1.5 dll has not changed recently, that seems weird, unless you admit that it has been a LONG time since your previous cygwin upgrade. > I am not asking to take responsibility for non-Cygwin executables > but to offer a hint as to what could possibly cause this failure. And I'm saying I don't know, nor can I, since on the surface, q has nothing to do with cygwin and nothing has really changed in recent cygwin 1.5 releases that should have any effect on non-cygwin apps. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpnECwACgkQ84KuGfSFAYBbFwCgxnelW92uB6lx+ksKvQ5sGETA p3cAoIOsr9jEwSrvdcwa94/WGzI7UH9q =XlGF -----END PGP SIGNATURE----- -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple