zsh-workers
 help / color / mirror / code / Atom feed
From: Dave Yost <Dave@Yost.com>
To: zsh-workers@sunsite.dk
Subject: 'pushd +2' rotates rather than extracts
Date: Wed, 16 Jun 2004 14:48:32 -0700	[thread overview]
Message-ID: <pdy98830611043cbcf66d1c36de@[192.168.1.2]> (raw)

This is how tcsh works with 'dextract' set:

% dirs
/tmp/a /tmp/b /tmp/c /tmp/d /tmp/e 
% pushd +2
0       /tmp/c
1       /tmp/a
2       /tmp/b
3       /tmp/d
4       /tmp/e

That is also how I believe zsh is documented to work (and how I would like it to work).

But here is what zsh does:

202 Z% echo $ZSH_VERSION
4.2.0
Z% dirs
/tmp/a /tmp/b /tmp/c /tmp/d /tmp/e
Z% pushd +2
/tmp/c /tmp/d /tmp/e /tmp/a /tmp/b
Z% 


             reply	other threads:[~2004-06-17  2:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 21:48 Dave Yost [this message]
2004-06-17  3:35 ` Vincent Stemen
2004-06-17  5:13 ` Bart Schaefer
2004-06-17  7:17   ` Vincent Stemen

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='pdy98830611043cbcf66d1c36de@[192.168.1.2]' \
    --to=dave@yost.com \
    --cc=zsh-workers@sunsite.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).