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
>>
On Wed, Mar 28, 2012 at 10:48 PM, Chet Ramey wrote:
> On 3/27/12 2:17 PM, Yichao Yu wrote:
>> So is it possible to set COMP_POINT as the number of characters
>> between 0 and rl_point (if it is also bad to break libreadline api by
>> setting rl_point as that.) without screwing up other part of the
On 3/27/12 2:17 PM, Yichao Yu wrote:
> So is it possible to set COMP_POINT as the number of characters
> between 0 and rl_point (if it is also bad to break libreadline api by
> setting rl_point as that.) without screwing up other part of the code?
> (I hope this fix would be no more than searching
So is it possible to set COMP_POINT as the number of characters
between 0 and rl_point (if it is also bad to break libreadline api by
setting rl_point as that.) without screwing up other part of the code?
(I hope this fix would be no more than searching for rl_point and
replace wherever necessary.)
On 3/22/12 6:59 PM, yyc1...@gmail.com wrote:
> Bash Version: 4.2
> Patch Level: 24
> Release Status: release
>
> Description:
> The variable COMP_POINT is actually set to the size (not the length)
> of the command line before the cursor, whereas ${#COMP_LINE} returns the
> length of the
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local
