[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange hostname completions after unset HOSTFILE
From: |
Chet Ramey |
Subject: |
Re: Strange hostname completions after unset HOSTFILE |
Date: |
Sun, 02 Aug 2009 15:01:56 -0400 |
User-agent: |
Thunderbird 2.0.0.22 (Macintosh/20090605) |
Freddy Vulto wrote:
> Bash Version: 3.2
> Patch Level: 48
> Release Status: release
>
> Description:
> The manual says that upon unsetting HOSTFILE, the hostname list is
> cleared:
>
> HOSTFILE
> Contains the name of a file in the same format as /etc/hosts
> that should be read when the shell needs to complete a hostname.
> The list of possible hostname completions may be changed while
> the shell is running; the next time hostname completion is
> attempted after the value is changed, bash adds the contents of
> the new file to the existing list. If HOSTFILE is set, but has
> no value, bash attempts to read /etc/hosts to obtain the list of
> possible hostname completions. When HOSTFILE is unset, the
> hostname list is cleared.
>
> but when I do so, instead of returning nothing, `compgen -A
> hostname' returns strange data.
Thanks for the report. This will be fixed in the next release of bash.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/