Re: cd, pwd and symlinks

[Peter Stephenson <pws@xxxxxxxxxxxxxxxxx>]

"Bart Schaefer" wrote:
> Certainly there should be at least ONE mode in which "cd .." simply does
> chdir(".."), and right now NO mode does so (even after PWS's patch).  I
> don't believe any of 3.1.<0-5> did this correctly either.

Aha.  You mean if I rename a parent directory, then even with chaselinks
set it gets confused.  This does seem to be the case.  That's annoying,
because pwd prints the right value.  It would certainly be nice to think
that chaselinks is always going to do the right thing, no funny business
(i.e. no turning .. into $PWD/..).

> } Now we have a mixture of the two styles, which isn't working, and
> } making it more complicated isn't going to help. Let's just have the
> } two ways of working, with an option to switch between them.
> 
> This is essentially my feeling too, except that I think we can do better
> in the failure cases.

With some clearer documentation on the subject, this could work ---
chaselinks does Zefram's 1, nochaselinks does logical directories, and if
you want the shell to be careful about non-existent directories you have to
move over to Hotel Chaselinks.  (I don't think most users want either/or
behaviour, they want the shell to do the right thing all the time, without
them having to tell it what that is, which is largely how the cd code
arose, and why it's a mess.)  But somebody's going to have to write this,
and it's unlikely to be me this time.

I'll leave out 8084 for now.

-- 
Peter Stephenson <pws@xxxxxxxxxxxxxxxxx>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy