X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_73,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <1243880825.24976.1318228015@webmail.messagingengine.com> References: <1243880825 DOT 24976 DOT 1318228015 AT webmail DOT messagingengine DOT com> Date: Mon, 1 Jun 2009 15:14:25 -0400 Message-ID: <7e08cc0906011214m6e0e4075l8d9223954be9e5e0@mail.gmail.com> Subject: Re: urxvt-X terminfo and Bash readline From: Dan Moulding To: cygwin AT cygwin DOT com 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 Precedence: bulk List-Id: List-Unsubscribe: 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 > I guess I could make it automatic even > then, by require:ing tic0...but then everybody, even those who don't > need it, would install tic0, the "old" terminfo0 database, and all of > the (old) ncurses libraries that tic0 needs. Plus, that runs against my > attempt to slowly phase out the "old" database... Admittedly, I'm part of the unwashed masses, terminfo-wise. So I don't know if this is kosher, but emacs seemed happy with the compiled terminfo that I made using the new tic. The only problem I had was that emacs was looking for it in the wrong place (I presume this is because my emacs [the latest Cygwin build] is compiled against the old ncurses). Would it be sufficient for the post-install script to copy the same terminfo file (built with new tic) to *both* locations, if the old database directory(ies) exists? I could understand why this would be bad if terminfos compiled by the new tic should only be compatible with programs compiled against the new ncurses, but I don't know if that's the case (it doesn't seem to be as far as I can tell based upon my limited testing of it so far). > > I know nothing of this. I didn't do anything "special" so I figure this > is the upstream default behavior of rxvt-unicode. I plan to update > rxvt-unicode to 8.x once cygwin-1.7 is released, so maybe we can revisit > this issue then. Seems plausible that it would be upstream behavior. The only reason I even noticed this is because rxvt seems to have a bug with escape characters in the Bash prompt. When they are there, it doesn't do the horizontal scrolling quite right, and it looks real ugly. Otherwise I'd have been fine with horizontal scroll mode... nah, actually I prefer it to just wrap, but I might not have been motivated enough to figure out why it was behaving differently from xterm if it did the horizontal scrolling properly. It's not a big deal since there is a straight-forward workaround. It just might be hard for some folks to figure out what the proper workaround is if they don't understand what drives the difference in behavior. Thanks for the explanations, Chuck. Much appreciated. Cheers, -- Dan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/