From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: PATCH: configure - use ncurses (not only ncursesw) before tinfo
Date: Wed, 28 Aug 2019 02:51:18 +0200 [thread overview]
Message-ID: <CAKc7PVCRtR3d=Bx+XsLebYFicEKPDq4qPMv782yvZGoO-ckd1A@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVC-Ms6NAOuw5SuEgfjTkdJwKoiMWP3H58f8QnzdL=hbuA@mail.gmail.com>
Just one more thing – if someone would have doubts as whether we
should so one directionally bind Zsh to ncurses, then let's notice
that the second library in the order enumeration – tinfo – is an
extracted terminal-sequences sublibrary taken out of ncurses.
On Tue, 27 Aug 2019 at 04:32, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> Hello,
> I've noticed that Zsh shipped with Mageia doesn't include zsh/curses
> module. Trying to build Zsh revealed the cause: Mageia ships with
> libncurses, not libncursesw and the relevant part in configure.ac
> says:
>
> termcap_curses_order="$ncursesw_test tinfo termcap $ncurses_test curses" ;;
>
> The width of the curses library is irrelevant to Zsh - it only needs
> the terminal sequences from the library, which aren't associated to
> any Unicode topic. As for the part that actually is relevant to the
> Unicode - the zsh/curses module - it is still better to build it
> without the multibyte support than not to build it at all.
>
> Not to say that libncurses libraries today do have multibyte support.
> So the conservative terminal-library order doesn't have any support in
> reality. The patch changes the order to:
>
> termcap_curses_order="$ncursesw_test $ncurses_test tinfo termcap curses" ;;
>
> --
> Sebastian Gniazdowski
> News: https://twitter.com/ZdharmaI
> IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
> Blog: http://zdharma.org
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
prev parent reply other threads:[~2019-08-28 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 2:32 Sebastian Gniazdowski
2019-08-28 0:51 ` Sebastian Gniazdowski [this message]
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='CAKc7PVCRtR3d=Bx+XsLebYFicEKPDq4qPMv782yvZGoO-ckd1A@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=zsh-workers@zsh.org \
/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).