Re: possible bug on readline

2010-01-18 Thread DennisW
On Jan 18, 11:01 am, Chet Ramey wrote: > On 1/18/10 12:40 AM, Samus_ wrote: > > > hello,  I had this on my shell: fgrep "$(nl_join " templates/ > > advertiser/campaign* and when tried to perform readline's glob-expand- > > word I got some parse errors, I'm not sure if it is a bug or the > > expect

Re: possible bug on readline

2010-01-18 Thread Chet Ramey
On 1/18/10 12:40 AM, Samus_ wrote: > hello, I had this on my shell: fgrep "$(nl_join " templates/ > advertiser/campaign* and when tried to perform readline's glob-expand- > word I got some parse errors, I'm not sure if it is a bug or the > expected behaviour because the line isn't functional code

possible bug on readline

2010-01-18 Thread Samus_
hello, I had this on my shell: fgrep "$(nl_join " templates/ advertiser/campaign* and when tried to perform readline's glob-expand- word I got some parse errors, I'm not sure if it is a bug or the expected behaviour because the line isn't functional code however I'm not sure if that should affect

Re: possible bug on readline

2010-01-18 Thread DennisW
On Jan 17, 11:40 pm, Samus_ wrote: > to reproduce simply try to glob-expand the following code: "$(" * You can reproduce that without the asterisk. I doubt that that's a bug in readline. The errors you're getting are from tab-completion which is done in a script. It's not handling the quotes pro