bug-bash
[Top][All Lists]
Advanced

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

why is 'direxpand' converting relative paths to absolute?


From: Linda Walsh
Subject: why is 'direxpand' converting relative paths to absolute?
Date: Sun, 16 Aug 2015 14:54:45 -0700
User-agent: Thunderbird

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 <address@hidden> 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?)





reply via email to

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