From: Adam Spiers <adam@thelonious.new.ox.ac.uk>
To: zsh-users@sunsite.auc.dk
Subject: Re: cd, pwd and symlinks
Date: Mon, 27 Sep 1999 14:02:04 +0100 [thread overview]
Message-ID: <19990927140204.A10336@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <19990927105103.A21392@youkaidi.irisa.fr>
Hubert Canon (Hubert.Canon@irisa.fr) wrote:
> Hi,
>
> I have strange behaviours with symlinks to directories.
[snip]
Put `setopt chaselinks' or `setopt chasedots' in your .zshrc. From
the info pages:
CHASE_DOTS
When changing to a directory containing a path segment `..' which
would otherwise be treated as cancelling the previous segment in
the path (in other words, `foo/..' would be removed from the path,
or if `..' is the first part of the path, the last part of $PWD
would be deleted), instead resolve the path to the physical
directory. This option is overridden by CHASE_LINKS.
For example, suppose /foo/bar is a link to the directory /alt/rod.
Without this option set, `cd /foo/bar/..' changes to /foo; with it
set, it changes to /alt. The same applies if the current directory
is /foo/bar and `cd ..' is used. Note that all other symbolic
links in the path will also be resolved.
CHASE_LINKS (-w)
Resolve symbolic links to their true values when changing
directory. This also has the effect of CHASE_DOTS, i.e. a `..'
path segment will be treated as referring to the physical parent,
even if the preceeding path segment is a symbolic link.
next prev parent reply other threads:[~1999-09-27 13:03 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 [this message]
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
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=19990927140204.A10336@thelonious.new.ox.ac.uk \
--to=adam@thelonious.new.ox.ac.uk \
--cc=adam@spiers.net \
--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).