Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: cygwin build problem - undefined setupterm
- X-seq: zsh-workers 14061
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: "Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx>, "ZSH Workers Mailing List" <zsh-workers@xxxxxxxxxx>
- Subject: Re: cygwin build problem - undefined setupterm
- Date: Sat, 21 Apr 2001 19:17:47 +0000
- In-reply-to: <000601c0ca5f$aadba880$21c9ca95@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <000601c0ca5f$aadba880$21c9ca95@xxxxxxxxxxxxxx>
On Apr 21, 4:36pm, Andrej Borsenkow wrote:
} Subject: cygwin build problem - undefined setupterm
}
} AFAIK setupterm belongs to curses interface suite and does not exist in
} termcap (it was not there before, it came with Clint's patches). Clint, you
} most probably have (n)curses in disguise ... and not the real termcap.
} Moreover, we already have terminal setup code in zsh main - it should not
} be duplicated (probably).
I believe setupterm() does not do terminal setup -- rather it assigns to
the TERM environment variable and to the TERMCAP or TERMINFO environment
variables as appropriate.
Of course it's going to do this "behind zsh's back" so if someone has done
something like `typeset -T TERMCAP tc' the linkage between those parameters
is going to be broken by setupterm().
There's also some issue of the interaction of setupterm() with LINES and
COLUMNS, and whether use_env() needs to be called before setupterm().
These are definitely (n)curses things rather than old termcap.
--
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author