Re: [Bash-completion-devel] Weird compopt.exp unit test problem

2010-02-11 Thread Freddy Vulto
On 100211 09:11, Ville Skyttä wrote: On Wednesday 10 February 2010, Freddy Vulto wrote: On 100210 18:16, Ville Skyttä wrote: Maybe this is what you meant above put in other words, but removing the -re {a\\\'b/c} { block from compgen.exp or hacking the regexp so that it does not match

Re: [Bash-completion-devel] Weird compopt.exp unit test problem

2010-02-11 Thread Freddy Vulto
On 100211 23:44, Ville Skyttä wrote: No objections, go ahead. I'm not worried at all about adding to the time taken by the tests if it makes them more reliable. I think we need to find a mean/middle. I'd like to run the tests as fast as possible when running the tests manually during

Re: [Bash-completion-devel] Weird compopt.exp unit test problem

2010-02-10 Thread Ville Skyttä
On Tuesday 09 February 2010, Crestez Dan Leonard wrote: On Sun, 2010-02-07 at 21:24 +0200, Ville Skyttä wrote: Huh, why does it end up invoking d $TESTDIR instead of cd $TESTDIR, and I suppose the first char of the { set; ... command got lost too? I tried bisecting but didn't find any

Re: [Bash-completion-devel] Weird compopt.exp unit test problem

2010-02-10 Thread Ville Skyttä
On Wednesday 10 February 2010, Freddy Vulto wrote: On 100210 18:16, Ville Skyttä wrote: Maybe this is what you meant above put in other words, but removing the -re {a\\\'b/c} { block from compgen.exp or hacking the regexp so that it does not match makes the problem go away for me. I don't

Re: [Bash-completion-devel] Weird compopt.exp unit test problem

2010-02-09 Thread Crestez Dan Leonard
On Sun, 2010-02-07 at 21:24 +0200, Ville Skyttä wrote: Huh, why does it end up invoking d $TESTDIR instead of cd $TESTDIR, and I suppose the first char of the { set; ... command got lost too? I tried bisecting but didn't find any particular commit that causes this so I suppose it's