Re: [Bash-completion-devel] _get_cword breaks with non-ascii characters when completion files

2010-04-12 Thread Guillaume Rousse
Le 10/04/2010 12:30, Freddy Vulto a écrit : I made a test case for this problem, see commit 3d4941f. I have to change LC_CTYPE=C to see the problem, probably because my default locale is en_US? You can run the test case(s) with: ./run ./unit/_filedir.exp I was able to move the fix

Re: [Bash-completion-devel] _get_cword breaks with non-ascii characters when completion files

2010-04-10 Thread Freddy Vulto
I made a test case for this problem, see commit 3d4941f. I have to change LC_CTYPE=C to see the problem, probably because my default locale is en_US? You can run the test case(s) with: ./run ./unit/_filedir.exp I was able to move the fix centrally to _quote_readline_by_ref in commit

Re: [Bash-completion-devel] _get_cword breaks with non-ascii characters when completion files

2010-04-03 Thread Guillaume Rousse
Le 01/04/2010 22:58, Guillaume Rousse a écrit : With pure ascii, $COMP_POINT = ${#COMP_LINE} = 11, meaning the test is true, but with non ascii chars, $COMP_POINT = 13 and ${#COMP_LINE} = 12, meaning the test is false. It seems like an utf8 issue, with bash (or readline) miscouting string with