From: Peter Stephenson <pws@csr.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: configure should have --with-ncurses and --with-ncursesw
Date: Thu, 4 Jan 2007 11:19:28 +0000 [thread overview]
Message-ID: <20070104111928.5e156466.pws@csr.com> (raw)
In-Reply-To: <20061225012304.GC31010@ay.vinc17.org>
Vincent Lefevre <vincent@vinc17.org> wrote:
> The problem is that zsh uses the curses API by default, so that
> currently, the only way to use the ncurses library is to install
> curses compatibility link (ncurses doesn't install them, but
> Linux distributions and Mac OS X do). The problem occurs when
> the user wants to install a newer version of ncurses (from
> upstream) in /usr/local, /opt/local or whatever. As zsh uses
> curses by default, it uses the old ncurses library (which, in
> the case of Mac OS X, is buggy).
>
> To be able to use ncurses by default, I had to change the configure
> script:
>
> - termcap_curses_order="tinfo curses ncurses termcap"
> + termcap_curses_order="ncurses tinfo curses termcap"
That looks harmless: I can't see why there might be a good reason for
preferring curses to ncurses. I'll have a go at this when I'm back in
normal operation (my home laptop power supply has died and I'm still
reeling from being back at work).
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
next prev parent reply other threads:[~2007-01-04 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 14:38 Vincent Lefevre
2006-12-18 15:46 ` Peter Stephenson
2006-12-19 16:12 ` DervishD
2006-12-19 16:22 ` Peter Stephenson
2006-12-25 1:23 ` Vincent Lefevre
2007-01-04 11:19 ` Peter Stephenson [this message]
2007-01-05 13:51 ` 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=20070104111928.5e156466.pws@csr.com \
--to=pws@csr.com \
--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).