X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.1 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,SARE_MSGID_LONG45,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 5 May 2010 05:59:16 +0100 Message-ID: Subject: Re: Resizing a terminal window From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 J. David Boyd wrote: > I don't think it is a Cygwin issue at all. =C2=A0And, I'm certain it is a > remote server problem, as it works on many boxes. > > I was just looking for some help and ideas, and the Cygwin list seemed a > good place to start since I use Cygwin. Right. This list is all about the misery of using Cygwin though. > =C2=A0I re-discovered the > shopt parameter of checkwinsize, which is what controls Bash monitoring > the window size from my prior message. Bash also sets LINES and COLUMNS when it receives a SIGWINCH ("window change") signal, apparently independent of 'checkwinsize'. Only the foreground process gets that signal though. So without 'checkwinsize', the setting of those variables depends on whether bash was in the foreground when the terminal was resized. Andy -- 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