zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: 3.0.6-pre-4: COLUMNS/LINES environment handling
Date: Tue, 15 Jun 1999 15:45:06 +0400	[thread overview]
Message-ID: <002601beb724$839e5510$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <990614094301.ZM19130@candle.brasslantern.com>

>
> Now, somebody who has a copy of the actual POSIX shell spec should tell
> us if the above is reasonable.  Zoltan, are you out there?
>

This is available online: http://www.opengroup.org/onlinepubs/7908799/toc.htm
(Single Unix V2)

 Other Environment Variables
COLUMNS
A decimal integer > 0 used to indicate the user's preferred width in column
positions for the terminal screen or window. (See column position .) If this
variable is unset or null, the implementation determines the number of columns,
appropriate for the terminal or window, in an unspecified manner. When COLUMNS
is set, any terminal-width information implied by TERM will be overridden. Users
and portable applications should not set COLUMNS unless they wish to override
the system selection and produce output unrelated to the terminal
characteristics. The default value for the number of column positions is
unspecified because historical implementations use different methods to
determine values corresponding to the size of the screen in which the utility is
run. This size is typically known to the implementation through the value of
TERM or by more elaborate methods such as extensions to the stty utility, or
knowledge of how the user is dynamically resizing windows on a bit-mapped
display terminal. Users should not need to set this variable in the environment
unless there is a specific reason to override the implementation's default
behaviour, such as to display data in an area arbitrarily smaller than the
terminal or window.

Note, that neither stty nor "General Terminal Inteface" description say any word
about the whole stuff :-)

In any case, I think the proposed order is correct and patch for 3.1.5 is
welcome.

/andrej

> How much of all that needs to go in the manual?  Lots of it should go in
> the FAQ, including remarks about how it is broken in various versions if
> we can figure that out.
>

We definitely have to describe, how COLUMNS/LINES are used/set by shell.

/andrej


  parent reply	other threads:[~1999-06-16 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-14  9:43 Bart Schaefer
1999-06-14 17:23 ` Tatsuo Furukawa
1999-06-15  8:10 ` Peter Stephenson
1999-06-15 11:45 ` Andrej Borsenkow [this message]
1999-06-16 12:47 ` Peter Stephenson
1999-06-17 11:39 ` Andrej Borsenkow
1999-06-17 15:22   ` Bart Schaefer
1999-06-17 17:01     ` Geoff Wing

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='002601beb724$839e5510$21c9ca95@mow.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).