[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Re: problems with bash-complete: doubling prefix@
From: |
Deliverable Mail |
Subject: |
[Gnu-arch-users] Re: problems with bash-complete: doubling prefix@ |
Date: |
Thu, 17 Mar 2005 21:48:48 -0500 |
An even simpler example, which is for realistic use: you want to tag a
project from address@hidden archive to a local project. I
use the underscore, _ to show where the cursor stops.
tla tag jb_
TAB
tla tag address@hidden
TAB
tla tag address@hidden
In general, any attempt to get a completion of a fully qualified name
such as address@hidden/tlacontrib--devo--1.2
will double the prefix before @ right after hitting the / and getting
c--b--v. One has to go back and manually undouble the prefix if you
want any further completion.
Creating plain files address@hidden and address@hidden shows that bash handles
them OK,
but mixes with e-mail names on my box, so I have to escape \@ -- then
it completes them fine, without doubling the prefix. There's
something about that @ deep inside tla completions...
Cheers,
Alexy
On Thu, 17 Mar 2005 20:12:32 -0500, Deliverable Mail
<address@hidden> wrote:
> Try the following: say, you have an archive address@hidden
> (from http://mirrors.sourcecontrol.net/-"-/ where
> tlacontrib--devo--1.2 contains bash-complete). You want to browse it.
>
> tla abrowse jblack
> TAB
> tla abrowse address@hidden
>
> # trailing space after 2004, all is fine... yet!
>
> now, backspace over some characters in the tail and TAB again:
>
> tla abrowse address@hidden
> TAB
> tla abrowse address@hidden
>
> So, the PREFIX before @ doubles upon two completions.
>
> I first noticed it when created archives with names address@hidden and
> address@hidden
> Then teh second TAB doubles the prefix 1 even earlier:
>
> tla abrowse 1
> TAB
> tla abrowse address@hidden
> y
> tla abrowse address@hidden
>
> The code in tla-bash-complete, aside from forgetting 0-9 in _archives,
> has no special treatment for @. But @ appears heavily used as a
> parameter. I wonder whether this is a bug in bash... And I have the
> latest bash 3.00. Any ideas as to what may be going on/how to
> alleviate it (backlashing something)?
>
> Cheers
> Alexy
>