bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why escape char `:' with `\' when auto completing filenames?


From: Clark J. Wang
Subject: Re: Why escape char `:' with `\' when auto completing filenames?
Date: Mon, 21 Feb 2011 10:16:13 +0800

On Mon, Feb 21, 2011 at 9:21 AM, Chet Ramey <address@hidden> wrote:

> On 2/18/11 6:52 AM, Clark J. Wang wrote:
>
> >
> > Sth was wrong for my testing. I removed @ from COMP_WORDBREAKS but
> > afterwards one bind command (bind "set bell-style none") added @ back.
>
> I can't reproduce this:
>
> $ echo $BASH_VERSION
> 4.2.0(22)-maint
> $ echo ${COMP_WORDBREAKS}
> "'@><=;|&(:
> $ COMP_WORDBREAKS=${COMP_WORDBREAKS/@/}
> $ echo ${COMP_WORDBREAKS}
> "'><=;|&(:
> $ bind 'set bell-style none'
> $ echo ${COMP_WORDBREAKS}
> "'><=;|&(:
>
>
I can reproduce this in my 2000+ lines of bashrc but I can't if I run the
command from the command line. I'll see what's the problem.


> Bash hostname completion is independent of the more-recently-added
> programmable completion, which I suspect you might be using.
>
> The default bash completion breaks words at @ and attempts to complete
> hostnames from its own internal list.  Look at the description of
> HOSTFILE and the readline `complete' function in the manual page.
>
> There is a shell option (`hostcomplete') to turn this on and off.
>
> Chet
>
> --
> ``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/
>



-- 
Clark J. Wang


reply via email to

[Prev in Thread] Current Thread [Next in Thread]