bug-bash
[Top][All Lists]
Advanced

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

Re: Problem: completion changes user-relative path into absolute path br


From: Chet Ramey
Subject: Re: Problem: completion changes user-relative path into absolute path breaking relative-path usages
Date: Mon, 6 Mar 2017 09:42:14 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1

On 3/6/17 7:33 AM, L A Walsh wrote:

> Under 4.4:
> 
> Ishtar:../util-linux-2.29.2> mydiff ../conf<ESC>
> Ishtar:../util-linux-2.29.2> mydiff
> /home/tools/util-linux/year-yyyy/month-mmm/day-ddd/newwork/very_long_path/config-2292.sh
> 
> diff:
> /home/tools/util-linux/year-yyyy/month-mmm/day-ddd/newwork/very_long_path/archive//home/tools/util-linux/year-yyyy/month-mmm/day-ddd/newwork/very_long_path/config-2292.sh:
> No such file or directory
> diff:
> /home/tools/util-linux/year-yyyy/month-mmm/day-ddd/newwork/very_long_path//home/tools/util-linux/year-yyyy/month-mmm/day-ddd/newwork/very_long_path/config-2292.sh:
> No such file or directory
> 
> 
> It throws away the relative path I need/expect and can't
> find anything, but worse it is very confusing throwing out
> an untyped path from the root.
> 
> Please, can this be fixed so the default is to not expand with
> those who want such unwieldy paths can apply some option?

I can't reproduce this with bash-4.4, even when setting `direxpand'
before performing completion on a pathname beginning with `../'.
It is possible that you or your vendor compiled bash with directory
expansion enabled by default (--enable-direxpand-default), which
turns this on.  If you don't want it, you can try turning off the
`direxpand' option.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/



reply via email to

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