X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: bash-3.2.5-7: COLUMNS and LINES variables are not set Date: Wed, 6 Dec 2006 04:13:59 +0000 (UTC) Lines: 23 Message-ID: References: <457611F0 DOT 9060606 AT gcmail DOT maricopa DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) 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 Mark Edgar gcmail.maricopa.edu> writes: > > It seems that bash for Cygwin does not set the COLUMNS and LINES shell > variables, neither at startup nor when WINCH is delivered. Defining > TIOCGWINSZ by including in lib/sh/winsize.c fixes the issue. Thanks for the hint! Look for 3.2.5-8 soon, once I also figure out how to fix the regression in 'printf %08x 0x90000000' (basically, bash's replacement asprintf is broken, although it avoids the coredump caused by asprintf in any cygwin earlier than the current snapshot. Have I ever mentioned on this list that it really bugs me that Chet acknowledges bug reports, and states that he has patched them in his local tree, but since his local tree is not public, I end up reproducing his work? And while I'm at it, I will mention that it would be nicer if Chet would use gnulib's replacement asprintf instead of rolling his own). I might also play with the postinstall script to be a little more aggressive in performing the /bin/sh upgrade, in case of different ownership between /bin/sh vs. /bin/bash. -- Eric Blake volunteer cygwin bash maintainer -- 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/