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 c...@case.edu http://cnswww.cns.cwru.edu/~chet/
