Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <19990511184117.25708.rocketmail@web106.yahoomail.com> Date: Tue, 11 May 1999 11:41:17 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: RE: bash sees all lines as 80 chars long To: "Stewart, Wayne" , cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- "Stewart, Wayne" wrote: -8<- > I then go to the Properties dialog for *this particular > window* by clicking on the Cygnus icon in the upper > left corner. After changing the window & buffer width > to '110', I select 'Apply properties to current window > only'. The window is now wider and 'stty size' returns > '50 110'. Holding down any letter key shows me bash > (readline) is still wrapping lines at 80 chars. > > If I execute 'kill -WINCH $$', bash (readline) will now > wrap the input command line correctly (at 110 chars, > or is it 109 chars - who cares, it looks right). > > So, I gather in your case you do not need to execute > 'kill -WINCH $$', and that your bash (readline) has > somehow seen the window resize operation and wraps > input lines at the correct line width? -8<- Aha, were discussing apples and oranges. The input line shifts to the left to make room on the right when I do your predescribed operation. Previously I was thinking output buffer, sorry for the confusion. Perhaps it has to do with wrapping modes in bash. === "Earnie Boyd" CYGWIN RELATED HELP: DOCUMENTATION: DLLHELP: ARCHIVE SEARCH: OR _________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com