X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com connect(): No such file or directory From: Hans Horn Subject: Re: Resizing a terminal window Date: Wed, 05 May 2010 08:40:42 -0700 Lines: 38 Message-ID: References: <4BE0903A.3030207@towo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 5/5/2010 8:28 AM, J. David Boyd wrote: > Thomas Wolff writes: > >> Am 04.05.2010 16:03, schrieb J. David Boyd: >>> ... >>> >>> Locally, I can use the mouse to resize a window, and the $COLUMNS and >>> $LINES variables are automatically filled in. >>> >>> On many remote xterm sessions, they aren't. >>> >>> Does anyone have any idea where to start figuring out what is wrong, and >>> what I can do to correct it? >>> >> LINES and COLUMNS are legacy mechanisms which may serve as a >> workaround if the system doesn't otherwise handle screen size changes >> properly. They should not be needed on modern systems where the tty >> driver maintains the information. >> (You may note that mintty has not set them initially but they get set >> on resize - by whatever means... - while in a cygwin console they are >> not used at all.) >> So if you happen to have these variables set on a system which does >> not maintain them, they don't get changed on resize and confuse your >> environment. In most cases the best remedy is to just unset them - >> does that help? >> >> ------ >> Thomas > > Sadly enough, the system I am connecting to, SUSE Linux, does use them, > and the checkwinsize shopt BASH function, but, somehow, not > correctly.... Just for curiosity: are you using 'expect' to log to the remote system? If so, you'd need you modify your expect script to handle SIGWINCH properly. Let me know... H. -- 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