zsh-users
 help / color / mirror / code / Atom feed
From: John S Cooper <jsc@Eng.Sun.COM>
To: zsh-users@math.gatech.edu
Cc: john.cooper@Eng.Sun.COM
Subject: `popd' is blocked on non-existent directory
Date: Tue, 15 Oct 1996 19:02:01 -0700	[thread overview]
Message-ID: <199610160202.TAA04520@kontiki.Eng.Sun.COM> (raw)


Under zsh 3.0.0, if a directory in the directory stack is removed, popd
seems to get "blocked".  In 2.5, the non-existent directory would just be
removed from the stack.  Here's what happens:

1175 kontiki%> dirs -v                                                  ~/elisp
0       ~/elisp
1       ~/elisp/foo
2       ~/elisp/foo/tm
3       ~Sputnik/sdtmail
1176 kontiki%>                                                          ~/elisp
1176 kontiki%> popd                                                     ~/elisp
popd: no such file or directory: /space/jsc/elisp/foo
1177 kontiki%> dirs -v                                                  ~/elisp
0       ~/elisp
1       ~/elisp/foo
2       ~/elisp/foo/tm
3       ~Sputnik/sdtmail
1178 kontiki%>                                                          ~/elisp


I'm now unable to pop the stack back past the non-existent "~/elisp/foo"
directory.  I know I can `cd -3' but it would be much better to have the
non-existent stuff cleaned out of the stack.

Is there a way to get the old behavior, i.e. have all non-existent
directories removed from the stack?

Also, when there's only one entry left on the dir stack, (I think) a popd
used to remove it and pop me to my home directory.  This is no longer the
case in 3.0.0 .

Thanks,

    --- John.


             reply	other threads:[~1996-10-16  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-16  2:02 John S Cooper [this message]
1996-10-16  5:26 ` Bart Schaefer
1996-10-17  0:56   ` John S Cooper

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=199610160202.TAA04520@kontiki.Eng.Sun.COM \
    --to=jsc@eng.sun.com \
    --cc=john.cooper@Eng.Sun.COM \
    --cc=zsh-users@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).