zsh-workers
 help / color / mirror / code / Atom feed
From: Juha Leskel{ <jussa@lenkkari.cs.tut.fi>
To: zsh-workers@math.gatech.edu
Subject: Directory stack and pushd/popd in zsh-2.6-beta17
Date: Fri, 10 May 1996 12:51:48 +0300	[thread overview]
Message-ID: <199605100951.AA157121909@lenkkari.cs.tut.fi> (raw)


Hello!

First I would like to thank you for the beta17 release, I was really waiting
for the full character support.

Then to questions. I noticed that in this release popd builtin doesn't work
as it used to. It really doesn't change the working directory. I tried it
with and without pushd command ( I have autopushd option set ), but the
result was the same. I also tried to unset autopushd option and without my
chpwd function. I checked what is happening to the directory stack and
here is something funny:

myprompt % pwd
/disks/tennari/users/jussa
myprompt % dirs -v
0       /disks/tennari/users/jussa
1       /disks/lapikas2/bin
2       /disks/lapikas2/bin/X11
3       /disks/mono2/local
4       /usr
5       /
6       /disks/tennari/users
myprompt % popd
myprompt % pwd
/disks/tennari/users/jussa
myprompt % dirs -v
0       /disks/tennari/users/jussa
1       /disks/lapikas2/bin/X11
2       /disks/mono2/local
3       /usr
4       /
5       /disks/tennari/users
myprompt % 

popd buitin seems to take out directory stack entry numbered "1" and then
rearrange the rest of the stack and then change to directory entry numbered
"0" which is where we currently are!

So is this happening to everybody or am I doing something wrong here? Please
reply to me if you can help me, I am not on the zsh-workers list.

This is what I have:

ZSH_VERSION=2.6-beta17
DIRSTACKSIZE=100
HOSTTYPE=hpux9.05
Compiler: HP92453-01 A.09.77 HP C Compiler



		Juha Leskela



             reply	other threads:[~1996-05-10 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-10  9:51 Juha Leskel{ [this message]
1996-05-10 15:19 ` Anthony Heading

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=199605100951.AA157121909@lenkkari.cs.tut.fi \
    --to=jussa@lenkkari.cs.tut.fi \
    --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).