zsh-users
 help / color / mirror / code / Atom feed
From: Jahwan Kim <jahwan@math.lsa.umich.edu>
To: zsh-users@math.gatech.edu
Subject: Re: zsh always resets LINES to 24.
Date: Wed, 3 Sep 1997 21:15:54 -0400	[thread overview]
Message-ID: <19970903211554.32046@supernova.math.lsa.umich.edu> (raw)
In-Reply-To: <199709030440.AAA01426@hzoli.home>; from Zoltan Hidvegi on Wed, Sep 03, 1997 at 12:40:18AM -0400

Quoting Zoltan Hidvegi (hzoli@frontiernet.net):
[snip]
[snip the clear explanation he gave]
[snip the patch]

    Thank you for the wonderful explanation.  I, as a user, want to point two
facts: 
    
    (1) The current behavior of zsh w.r.t. LINES and COLUMNS is not what it
should be.  As far as I experienced, bash and zsh don't have any problem
with LINES and COLUMNS.  I don't have their sources at hand, but zsh-workers
can take a look at them and tell us what's the deal.

    (2) Also the manual doesn't describe the situation properly.  The manual 
lists LINES under 'The following parameters are used by the shell:', not
under 'The following parameters are automatically set by the shell:', where
I think it should be.  And the sentences 'The number of lines for this
terminal session.  Used for printing select lists and for the line editor'
doesn't say anything about zsh resetting LINES.  Hopefully, this should be
fixed in the next release, IMHO.

    I agree with what others have suggested.  Treat LINES and COLUMNS as
magical variables, and whenever those are set by users within a shell, call
appropriate ioctl.

Cheers,
Jahwan


      parent reply	other threads:[~1997-09-04  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-03  2:55 Jahwan Kim
1997-09-03  4:40 ` Zoltan Hidvegi
1997-09-03  8:27   ` Andrew Main
1997-09-03 15:44     ` Bart Schaefer
1997-09-03 16:13       ` Andrew Main
1997-09-04  1:15   ` Jahwan Kim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19970903211554.32046@supernova.math.lsa.umich.edu \
    --to=jahwan@math.lsa.umich.edu \
    --cc=zsh-users@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).