zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: can't find termcap info
Date: Tue, 18 Sep 2001 12:19:41 -0700	[thread overview]
Message-ID: <010918121941.ZM8023@candle.brasslantern.com> (raw)
In-Reply-To: <20010918053813.C13299@hq.newdream.net>
In-Reply-To: <20010918145958.A17178@greux.loria.fr>
In-Reply-To: <20010918165111.B17411@greux.loria.fr>
In-Reply-To: <20010918155339.20305.qmail@web12504.mail.yahoo.com>
In-Reply-To: <20010918181329.A17722@greux.loria.fr>

On Sep 18,  5:38am, Will Yardley wrote:
> 
> i don't understand this fully (perhaps bart or someone can give a more
> depth explanation), but i believe that unless you specifically compile
> zsh with ncurses (or have a version that was compiled to work with
> ncurses) it uses some sort of system of its own.

No, that's not it.

Zsh's configure looks for the smallest set of libraries that will provide
support for ZLE.  (As in smallest memory footprint, or at least that was
the original intent.)  Curses is the heavyweight of the bunch, so that is
avoided unless nothing else will work (or unless you ask configure to use
it via --with-curses-terminfo).  Zsh's configure looks for termcap first,
then terminfo, and finally curses, except on some specific platforms where
that search order is known to be sub-optimal.

So the chances are that if termcap exists and you didn't pass any options
to configure, then termcap is the only thing that zsh will understand.

On Sep 18,  2:59pm, Vincent Lefevre wrote:
> 
> > export TERMCAP=/etc/termcap (terminfo is better if it works)
> 
> greux:~> export TERMCAP=$HOME/.termcap                                <14:54:42
> greux:~> TERM=nettle                                                  <14:54:55
> rlogin: connection closed.
> 
> Why???

Here's what you do:  Log in to greux.  Start a second copy of zsh inside the
first one, so that you're no longer working directly with the login shell.
Then try the above again and see if (a) the connection still closes or (b)
you get some error messages when the "nested" shell exits.

Then tell us about it.

On Sep 18,  4:51pm, Vincent Lefevre wrote:
> >  are you sure that the termcap and / or terminfo info for your
> > terminal type is correct?
> 
> It works with Mutt, less and emacs. But well, zsh doesn't say that it is
> incorrect; it says that it can't find the termcap info.

It's entirely possible that Mutt, less, emacs, and bash are using terminfo
(which is OK) while zsh is using termcap (which has something wrong).

> nettle|nettle terminal emulator (RISC OS):\
> 	:ke=:ks=:tc=rxvt:

Are you sure there's an rxvt entry?  What happens if you do

TERM=rxvt

?  Is there any value you can assign to TERM that does *not* produce the
warning?

On Sep 18,  6:13pm, Vincent Lefevre wrote:
> 
> Here, until I installed ncurses 5.2 (which is after I compiled zsh),
> tgetent didn't seem to exist; at least, there was no man page about
> this function.

Try "man curs_termcap".  However, tgetent() is unlikely to be the problem.


  parent reply	other threads:[~2001-09-18 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18 12:25 Vincent Lefevre
2001-09-18 12:38 ` Will Yardley
2001-09-18 12:59   ` Vincent Lefevre
2001-09-18 13:25     ` Will Yardley
2001-09-18 14:51       ` Vincent Lefevre
2001-09-18 15:53         ` a normal guy
2001-09-18 16:13           ` Vincent Lefevre
2001-09-18 16:28             ` a normal guy
2001-09-18 17:04               ` Vincent Lefevre
2001-09-18 19:19             ` Bart Schaefer [this message]
2001-09-18 20:39               ` Vincent Lefevre
2001-09-18 22:10                 ` Bart Schaefer
2001-09-18 22:50                   ` Vincent Lefevre
2001-09-18 23:17                     ` Bart Schaefer
2001-09-19 10:10                       ` Vincent Lefevre

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=010918121941.ZM8023@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).