zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Markku.Jarvinen@tpo.fi, zsh-workers@math.gatech.edu
Subject: Re: a bug in zsh?
Date: Thu, 25 Jul 1996 10:03:25 -0700	[thread overview]
Message-ID: <960725100325.ZM13654@candle.brasslantern.com> (raw)
In-Reply-To: Markku.Jarvinen@tpo.fi "a bug in zsh?" (Jul 25,  3:49pm)

On Jul 25,  3:49pm, Markku.Jarvinen@tpo.fi wrote:
} Subject: a bug in zsh?
}
} BUG: when option chaselinks is set and I run zsh on a host
}      which has automounted homedirectories command 'pwd'
}      does weird things (i.e. changes directory to some random
}      directory that was first mounted using automount).

That's because the automounter is implemented by mounting the directory
somewhere else and then setting up symlinks in the magic automount
directory to point to the actual mount location.  Zsh is doing the
right thing with respect to the symlinks.

} Any suggestions other than turning chaselinks off?

Yeah; turn the automounter off.

There might be something that could be done by checking the results of
stat() on ".." and "." [which zgetcwd() is already doing] and change
the behavior when ".." crosses over to a different logical device.  I'm
not sure what, though.  You'd have to get the original path used by cd
back, and start working *down* until you found the directory at which
the device change took place.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



      reply	other threads:[~1996-07-25 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-25 12:49 Markku.Jarvinen
1996-07-25 17:03 ` Bart Schaefer [this message]

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=960725100325.ZM13654@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=Markku.Jarvinen@tpo.fi \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).