zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users@sunsite.auc.dk
Subject: Re: cd, pwd and symlinks
Date: Tue, 28 Sep 1999 00:11:16 +0000	[thread overview]
Message-ID: <990928001116.ZM17774@candle.brasslantern.com> (raw)
In-Reply-To: <5lemfkez1d.fsf@tequila.cs.yale.edu>

On Sep 27,  7:05pm, Stefan Monnier wrote:
> Subject: Re: cd, pwd and symlinks
> >>>>> "Adam" == Adam Spiers <adam@thelonious.new.ox.ac.uk> writes:
> > Put `setopt chaselinks' or `setopt chasedots' in your .zshrc.  From
> > the info pages:
> 
> I must say I don't like the names and defaults.  The names give the
> impression that chasing links is a very unusual feature while it's the
> normal unix behavior.

It's not, however, the normal zsh behavior, and has not been for a very long
time.  It may even date back to a specific personal preference of Falstad's;
I don't recall for certain now.

> But apart from that, I'm more often annoyed by `pwd' not checking the
> value it returns

"pwd" is nothing more than a slightly fancified alias for "echo $PWD", and
PWD does not get reset every time zsh prints a prompt (unless you do it in
your precmd function).  Rather, it gets reset every time you "cd".

The builtin pwd in bash and (I think) ksh also have the same behavior.
There is no builtin pwd in tcsh, but tcsh does not reset $cwd following
such a "mv" command.

You can always put

	disable pwd

in your init files somewhere, to force zsh to run the external pwd command
instead.


  reply	other threads:[~1999-09-28  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-27  8:51 Hubert Canon
1999-09-27 13:02 ` Adam Spiers
1999-09-27 13:34   ` Hubert Canon
1999-09-27 13:42     ` Adam Spiers
1999-09-30 19:05       ` Adam Spiers
1999-09-27 23:05   ` Stefan Monnier
1999-09-28  0:11     ` Bart Schaefer [this message]
1999-09-28  0:47       ` Stefan Monnier
1999-09-29  1:11     ` Rob Windsor

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=990928001116.ZM17774@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-users@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).