[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A programmable completoin bug?
From: |
Clark J. Wang |
Subject: |
Re: A programmable completoin bug? |
Date: |
Mon, 5 Dec 2011 13:36:15 +0800 |
On Mon, Dec 5, 2011 at 13:15, Clark J. Wang <dearvoid@gmail.com> wrote:
> On Mon, Dec 5, 2011 at 11:42, Chet Ramey <chet.ramey@case.edu> wrote:
>
>> On 12/4/11 10:26 PM, Clark J. Wang wrote:
>> > On Mon, Dec 5, 2011 at 11:10, Chet Ramey <chet.ramey@case.edu
>> > <mailto:chet.ramey@case.edu>> wrote:
>> >
>> >
>> > I still can't reproduce it on Mac OS X or RHEL 5.7:
>> >
>> >
>> > It's weird. :) Any other settings can affect this? What can I do to
>> debug more?
>>
>> Well, if it were me, I'd fire up gdb and set a breakpoint in
>> pcomplete.c:gen_shell_function_matches. I wonder if you've got something
>> filtering out or ignoring those matches.
>>
>> Chet
>> --
>> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>> ``Ars longa, vita brevis'' - Hippocrates
>> Chet Ramey, ITS, CWRU chet@case.edu
>> http://cnswww.cns.cwru.edu/~chet/
>>
>
> After more investigation I found that it's caused by "set
> completion-ignore-case on". After turning completion-ignore-case off it
> works fine. You can give it a try.
>
Note that I used the `bind' command to turn `completion-ignore-case' on/off
and I did not use $HOME/.inputrc, in case that makes a difference.
>
> Still remember another bind issue (
> http://lists.gnu.org/archive/html/bug-bash/2011-03/msg00094.html ) I
> reported before? Maybe it's the similar problem.
>
> --
> -Clark
>
>
--
-Clark