On Tue, Nov 02, 2010 at 02:10:43PM -0700, Daniel Colascione wrote:
>On 11/2/2010 1:56 PM, Eric Blake wrote:
>> On 11/02/2010 02:49 PM, dan.colascione wrote:
>>>
>>> + rl_add_defun ("shell-forward-word", bash_forward_shellword, -1);
>>> + rl_add_defun ("shell-backward-word", bash_backward_shellword, -1);
>>> + rl_add_defun ("shell-kill-word", bash_kill_shellword, -1);
>>> + rl_add_defun ("shell-backward-kill-word", bash_backward_kill_shellword,
>>> -1);
>>
>> Hmm, here, it probably makes more sense for me to bite the bullet and
>> port my cygwin-specific stuff from bash 3.2 into bash 4.1, rather than
>> trying to backport bash 4.1 stuff into my cygwin 3.2 build.
>>
>
>Getting 4.1 would be better, sure, but it's not available right now,
You know you're communicating with the bash package maintainer, right?
If he thinks that it makes sense to upgrade to a new version rather than
rolling a new, patched older version, then you can't really use the "4.1
isn't available" argument since his point is that he could make it
available. He's probably the only person who understands the tradeoffs.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
