[Bash-completion-devel] [bash-completion-Bugs][313583] _init_completion doesn't work well for command line that contain non ascii characters

bash-completion-bugs at alioth.debian.org bash-completion-bugs at alioth.debian.org
Thu Mar 22 22:45:20 UTC 2012


Bugs item #313583, was changed at 2012-03-22 18:26 by Yichao Yu
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313583&group_id=100114

Status: Open
Priority: 3
Submitted By: Yichao Yu (yuyichao-guest)
Assigned to: Nobody (None)
Summary: _init_completion doesn't work well for command line that contain non ascii characters 
Distribution: --Distribution-Agnostic--
Originally reported in: None
Milestone: 2.0
Status: None
Original bug number: 


Initial Comment:
the cur variable after calling this function doesn't contain the right string if there is non-ascii character in it.
all other variables are fine (including $words !!)
Moreover, what I have seen is, if there are n Chinese characters in this argument, it will contain n more variables from the following arguments! (so something must have gone wrong dealing with the length/size of the string~~)

Version and distribution used: bash-completion 1.99 from Archlinux official repo.

=D


----------------------------------------------------------------------

Comment By: Yichao Yu (yuyichao-guest)
Date: 2012-03-22 18:45

Message:
it's a bug of bash

----------------------------------------------------------------------

Comment By: Yichao Yu (yuyichao-guest)
Date: 2012-03-22 18:36

Message:
The bug is in the position calculation in __get_cword_at_cursor_by_ref


----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313583&group_id=100114



More information about the Bash-completion-devel mailing list