4
If in bash, I do "set -P
" then bash follows the "physical directory
structure" when doing "pwd
" and "cd ..
" etc, rather than the "logical
one" that might be defined via symlinks. Unfortunately, bash still
doesn't obey the physical directory structure for filename completion.
How can I get bash to respect my authority on this issue?
Thanks!
|>ouglas
P.S. Unfortunately, the same problem has now afflicted Emacs for opening files, etc. If anyone also knows how to also tell Emacs to respect my physical directory structure, then I'd also like to know the answer to that.
P.P.S. I don't know who decided that having some programs try to fathom your "logical directory structure" was a good idea, but it's not! Not unless you can convince every program in the world to do things this way, since having some programs use your physical directory structure, and having other ones use your logical directory structure is a recipe for confusion and annoyance.
I don't understand the problem. Are you not able to open files? Is bash completion getting the wrong path? – James Polley – 2010-01-05T23:21:47.793
That depends on what you mean by "wrong". Bash is not following the Unix meaning of "..", which is a real directory entry in a directory, and points to the physical parent directory. Instead bash is interpreting ".." to mean "strip one entry off the path that I took to get here".
I don't want to use this fancy newfangled meaning. I want the normal Unix meaning. – Douglas – 2010-01-06T19:42:30.907