From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: cd, pwd and symlinks
Date: Wed, 29 Sep 1999 03:29:44 +0000 [thread overview]
Message-ID: <990929032944.ZM21831@candle.brasslantern.com> (raw)
In-Reply-To: <E11W1H5-0001ev-00@crucigera.fysh.org>
On Sep 28, 6:42pm, Zefram wrote:
} Subject: Re: cd, pwd and symlinks
}
} Bart Schaefer wrote:
} >On Sep 28, 12:07pm, Peter Stephenson wrote:
} >} There's some reason why the code was changed
} >} to do all changes with absolute path --- maybe to simplify it, hur hur.
} >
} >As far as I can tell, this is something Zefram changed between 3.1.2 and
} >3.1.3, for which no patch was ever posted.
}
} I'm pretty sure it's not. That's one of the areas of the shell that I
} studiously avoided changing.
Ah. Further investigation reveals that this was already changed in 3.1.0;
I've checked the RCS files from that version that are on the FTP site. So
the next best guess is that Zoltan changed this; see the ChangeLog entry
for Thu Dec 5 03:59:45 1996, "Lots of other stuff."
} Given that we have to support [PWD], there are basically two sensible
} ways for it to work:
}
} 1. cd maps directly onto chdir(), doing everything the way the
} filesystem says.
}
} 2. $PWD is the shell's canonical idea of its current directory. cd with
} a relative pathname does text substitution using $PWD, and then does
} a chdir() to the resulting absolute pathname.
I generally agree with this viewpoint, but:
} Until 3.1.6, we had a pretty consistent 2.
I don't really agree with that last, the problem being that other parts
of the shell (particularly completion) didn't pay attention to the same
rules, which could lead to all sorts of odd stuff. I'm not sure we've
completely (ahem) fixed that, even yet.
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.
} 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.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-09-29 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5lemfkez1d.fsf@tequila.cs.yale.edu>
1999-09-28 10:07 ` Peter Stephenson
1999-09-28 16:42 ` Bart Schaefer
1999-09-28 17:42 ` Zefram
1999-09-29 3:29 ` Bart Schaefer [this message]
1999-09-29 9:33 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=990929032944.ZM21831@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).