From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4345 invoked from network); 6 May 2001 05:03:34 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 May 2001 05:03:34 -0000 Received: (qmail 19801 invoked by alias); 6 May 2001 05:03:30 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14232 Received: (qmail 19790 invoked from network); 6 May 2001 05:03:30 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) Date: Sun, 6 May 2001 09:03:27 +0400 (MSD) From: Andrej Borsenkow X-X-Sender: To: Subject: Re: terminfo values (was Re: do I win the "most pointless use of ZSH" award? ;)) In-Reply-To: <20010430164249.A18287@dman.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 30 Apr 2001, Clint Adams wrote: > > COLUMNS and LINES aren't immediately updated for me when I change text > > mode resolutions. Is there something I should do to make them as > > reliable as the tput values? > > This reminded me that a SIGWINCH will update $COLUMNS and $LINES, > and therefore tput and $COLUMNS and $LINES will be more reliable > than echotc/echoti/$termcap/$terminfo. > I don't see this as a problem for $termcap/$terminfo. They are supposed to return static values from external database; so far you have the same problem when using original functions (tgetstr etc). E.g. curses has special variables that held current lines/columns values. -andrej