From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk, Vincent Lefevre <vincent@vinc17.org>
Subject: Re: TERM problem under OSF
Date: Mon, 24 Sep 2001 15:52:15 +0000 [thread overview]
Message-ID: <1010924155216.ZM3531@candle.brasslantern.com> (raw)
In-Reply-To: <4abf0b6e0fvincent@vinc17.org>
As it's generally necessary to set both TERM and one of TERM(CAP|INFO),
initializing the terminal each time any one of those three changed would
be a waste of effort as often as not (because it would immediately be
initialized again when the other parameter changed).
However, we should at least document that assigning to TERM has this
effect, so that people would know that they need to reset it after they
change the others.
Index: Doc/Zsh/params.yo
===================================================================
diff -c -r1.6 params.yo
--- Doc/Zsh/params.yo 2001/07/10 09:05:18 1.6
+++ Doc/Zsh/params.yo 2001/09/24 15:46:43
@@ -993,7 +993,12 @@
)
vindex(TERM)
item(tt(TERM) <S>)(
-The type of terminal in use. This is used when looking up termcap sequences.
+The type of terminal in use. This is used when looking up termcap
+sequences. An assignment to tt(TERM) causes zsh to re-initialize the
+terminal, even if the value does not change (e.g., `tt(TERM=$TERM)'). It
+is necessary to make such an assignment upon any change to the terminal
+definition database or terminal type in order for the new settings to
+take effect.
)
vindex(TIMEFMT)
item(tt(TIMEFMT))(
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
parent reply other threads:[~2001-09-24 15:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4abf0b6e0fvincent@vinc17.org>]
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=1010924155216.ZM3531@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=vincent@vinc17.org \
--cc=zsh-workers@sunsite.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).