Re: Why escape char `:' with `\' when auto completing filenames?
From:
Chet Ramey
Subject:
Re: Why escape char `:' with `\' when auto completing filenames?
Date:
Sun, 20 Feb 2011 20:21:29 -0500
User-agent:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
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}
"'><=;|&(:
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 chet@case.edu http://cnswww.cns.cwru.edu/~chet/