On Mon, Aug 17, 2015 at 5:54 AM, Linda Walsh <b...@tlinx.org> wrote: > From the manpage I wouldn't have guess it changed > paths to absolute -- but would expand variables and wildcards > in the path. > > It doesn't seem to make alot of sense when there are other > ways to go from rel->abs, but not so many that just expand > vars or aliases on a dir. > Does anyone know why path conversion was built into it? >
I had the same problem months ago. See Chet's answer: http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00069.html -clark > > > > Linda Walsh wrote: > >> >> >> Andreas Schwab wrote: >> >>> Linda Walsh <b...@tlinx.org> writes: >>> >>> in bash 4.3.39, >>>> if I type a command, (like "."(source)) and a relative path >>>> like : ../conf<complete>, >>>> it expands the relative pathname to absolute pathnames. >>>> >>> >>> Worksforme. Make sure to run complete -r first. >>> >> --- >> You didn't say what version of bash you were using... but >> that may not be relative: >> >> It seems to be "direxpand" -- do you have it on or off. >> >> It is supposed to perform word expansion. It doesn't >> say it will convert relative paths to absolute. >> >> Has it always been that way? (I thought direxpand expanded >> variables in a path?) >> >> >> >
