From: Pedro Alves <palves@redhat.com>
To: Matthias Klose <doko@ubuntu.com>,
gdb-patches@sourceware.org, John Baldwin <jhb@freebsd.org>
Subject: Re: [patch] Allow to link with ncursesw
Date: Wed, 20 Sep 2017 21:22:00 -0000 [thread overview]
Message-ID: <e8d80005-3c3a-cff7-0164-858280117d89@redhat.com> (raw)
In-Reply-To: <efd9c02d-767f-bc13-0c1e-85dbc8a7acd8@ubuntu.com>
On 09/20/2017 08:51 PM, Matthias Klose wrote:
> On 20.09.2017 20:39, Pedro Alves wrote:
>> Did you reach out to readline/bash, see if they're willing
>> to try ncursesw before ncurses too? Don't we need at least
>> a local patch to our local readline copy, to avoid breaking
>> those that use it and have it link with ncurses?
>
> afaik, this is only the case if readline is linked with one of the curses
> libraries. However these days everybody seems to have readline linked to just
> tinfo, so this shouldn't be an issue?
Everybody on GNU/Linux, it seems. However, the Python bug
report talked about FreeBSD's readline linked with ncurses
Do you know whether they've switched to tinfo as well
meanwhile? [Adding John as FreeBSD maintainer.]
> Python itself doesn't link to a curses library, it uses the only which is used
> for readline.
>
And if readline doesn't use curses, what does Python do?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-09-20 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 10:29 Matthias Klose
2017-09-20 18:39 ` Pedro Alves
2017-09-20 19:52 ` Matthias Klose
2017-09-20 21:22 ` Pedro Alves [this message]
2017-09-20 21:25 ` Pedro Alves
2017-09-20 23:58 ` John Baldwin
2017-09-22 10:22 ` Pedro Alves
2017-09-25 18:34 ` John Baldwin
2017-09-26 15:27 ` Pedro Alves
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=e8d80005-3c3a-cff7-0164-858280117d89@redhat.com \
--to=palves@redhat.com \
--cc=doko@ubuntu.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox