On 12/17/11 6:52 AM, wiebittewas wrote:
> Bash Version: 4.2
> Patch Level: 10
> Release Status: release
>
> Description:
> typing 'echo $PWD/[TAB]' results in 'echo \$PWD/' instead of
> 'echo /'
> (all without single quotes of course...)
>
> This behaviour doesn't exist a
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-pc-linux-gnu' -DCO$
uname output: Linux dose 3.0.0-12-generic #20-Ubuntu S
On 12/11/11 1:13 AM, Alex Shinn wrote:
> I had initially been confused by the HISTTIMEFORMAT
> variable thinking it could be used to change what was
> written to the history file, rather than the output of the
> history command.
>
> Obviously it would have to be a separate variable, but
> the abi
On 12/11/11 3:41 PM, Raphaël Droz wrote:
> Example:
> $ var=$(id) foo
> completes with completion matches from id(1)
>
> This is problematic for cases like:
> LD_LIBRARY_PATH=$(find ...) cmd --
> where options are those from find(1).
>
> I didn't looked deeper but I guess the faulty part is in
>
