From: Peter Stephenson <pws@csr.com>
To: Mailing-list zsh-users <zsh-users@sunsite.auc.dk>
Subject: Re: TERM problem under OSF
Date: Mon, 24 Sep 2001 14:02:31 +0100 [thread overview]
Message-ID: <8944.1001336551@csr.com> (raw)
In-Reply-To: "Vincent Lefevre"'s message of "Mon, 24 Sep 2001 13:24:50 +0200." <4abefecae2vincent@vinc17.org>
Vincent Lefevre wrote:
> Setting TERM=$TERM after TERMINFO is changed should solve the problem,
> but why doesn't zsh detect when TERMINFO is changed?
It doesn't know anything about curses, nor termcap, and there are a whole
load of different implementations which might be linked in, as we've been
seeing recently. So there's no simple way of knowing whether TERMINFO is
relevant at all.
I suppose there's nothing to stop us doing some more
implementation-specific probing, now we have separate termcap and terminfo
modules, and shovelling some extra code into those, linking in the
appropriate version when necessary (echotc and echoti already depend on the
respective modules).
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next prev parent reply other threads:[~2001-09-24 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 11:24 Vincent Lefevre
2001-09-24 13:02 ` Peter Stephenson [this message]
2001-09-24 13:42 ` Vincent Lefevre
2001-09-24 15:02 ` Peter Stephenson
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=8944.1001336551@csr.com \
--to=pws@csr.com \
--cc=zsh-users@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).