This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated [experimental]: readline-5.2-2, libreadline6-5.2-2 - Bash-3.2-3
Angelo Graziosi <Angelo.Graziosi <at> roma1.infn.it> writes:
> The combination
> seems to solve the problems described in
> The problems still remain if one uses bash-3.1-9.
Then it sounds like an upstream limitation and not a bash specific problem,
where in the process of adding new hooks to readline 5.2 and using those new
hooks in bash 3.2, the upstream maintainer inadvertantly broke the semantics of
the old hooks in use by bash 3.1 (in other words, he kept the shared library
binary compatible, but not behaviorally compatible). If it bothers you enough,
then you should report it upstream (bug-bash AT gnu.org), and see if the
upstream maintainer would patch readline 5.2 to avoid breaking programs that
linked against readline 5.1. But since I won't be promoting readline 5.2 to
current without also promoting bash 3.2, it doesn't bother me enough to worry
about it unless someone were to report a program other than bash 3.1 that was
also affected by this change in the semantics. Bash tends to be the most
extreme user of all the hooks and knobs provided by the readline library; most
readline clients don't exercise all those knobs, and therefore don't care when
a hook added primarily for bash changes in semantics.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html