Re: Multiple Words on Bash Programmable Auto Completion

2008-10-02 Thread Matthew Woehlke
Chet Ramey wrote: Chet Ramey wrote: How come you didn't mention '-o nospace' when I was trying to write a completion for directory names from a non-PWD reference point? ;-) Did it exist then? :-) Did it not? I'm running 3.2-22.fc9 (3.2.33(1)-release). I'm referring to the thread http://pe

Re: Multiple Words on Bash Programmable Auto Completion

2008-10-02 Thread Chet Ramey
> Chet Ramey wrote: > How come you didn't mention '-o nospace' when I was trying to write a > completion for directory names from a non-PWD reference point? ;-) Did it exist then? :-) Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU[EMAIL PROTECTE

Re: Multiple Words on Bash Programmable Auto Completion

2008-10-02 Thread Matthew Woehlke
Chet Ramey wrote: Description: I don't know if this is a bug or not, but it has to do with programmable auto completion. Whenever the options have multiple words I don't get what I want. You can get filename-like quoting by specifying that readline should treat the matches returned by the c

Re: Multiple Words on Bash Programmable Auto Completion

2008-10-02 Thread Daniel Fleischman
Thank you, that's exactly what I wanted. On Thu, Oct 2, 2008 at 09:16, Chet Ramey <[EMAIL PROTECTED]> wrote: > > Description: > > I don't know if this is a bug or not, but it has to do with > programmable > > auto completion. Whenever the options have multiple words I don't get > what I > > w

Re: Multiple Words on Bash Programmable Auto Completion

2008-10-02 Thread Chet Ramey
> Description: > I don't know if this is a bug or not, but it has to do with programmable > auto completion. Whenever the options have multiple words I don't get what I > want. You can get filename-like quoting by specifying that readline should treat the matches returned by the completion fun