[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: COMP_POINT is not set correctly when there is non-ascii characters i
Re: COMP_POINT is not set correctly when there is non-ascii characters in the command line.
Thu, 05 Apr 2012 15:19:36 -0400
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
On 3/28/12 11:11 PM, Yichao Yu wrote:
>> Pretty much everything else in bash uses characters, which may be bytes
>> depending on the locale.
>> Can someone who's more familiar with the bash completion package tell me
>> whether or not it uses COMP_POINT at all? That's about that only thing
>> I can think of that would use it.
> It DOES use COMP_POINT. And this is the most annoy thing and also how
> I notice the issue. I reported a bug for bash-completion here
> and soon discovered this is a bush issue.
Yep, it seems pretty clear that the appropriate fix is to make COMP_POINT
a locale-aware character count rather than a locale-independent byte
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU address@hidden http://cnswww.cns.cwru.edu/~chet/
|[Prev in Thread]
||[Next in Thread]|
- Re: COMP_POINT is not set correctly when there is non-ascii characters in the command line.,
Chet Ramey <=