Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #11356

why is 'direxpand' converting relative paths to absolute?

Show key headers only | View raw

>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?



Linda Walsh wrote:
> 
> 
> Andreas Schwab wrote:
>> Linda Walsh <bash@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?)
> 
> 

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

why is 'direxpand' converting relative paths to absolute? Linda Walsh <bash@tlinx.org> - 2015-08-16 14:54 -0700

csiph-web