From: "Heading, Anthony" <heading_anthony@jpmorgan.com>
To: "Danek Duvall" <duvall@dhduvall.student.Princeton.EDU>
Cc: zsh-workers@math.gatech.edu
Subject: RE: PUSHD_TO_HOME problem
Date: 12 Nov 1995 01:51:27 U [thread overview]
Message-ID: <n1395999439.7422@smtpgwprod.ny.jpmorgan.com> (raw)
> However, I don't like the behaviour your patch produces.
Oh dear. Sorry about that.
> I want cd to be able to swap the top two dirs, just like pushd does. [...]
> Obviously, it's not that big a deal; I can alias cd to pushd if I want.
You can indeed. That was really all that AUTO_PUSHD used to do. But the
consequence was that a naked cd "broke", hence the need for PUSHD_TO_HOME.
I hope my patch allows for all comers. The old behaviour is exactly
replicable, I think, by aliasing cd to pushd. But if you don't alias
you get cd=>home and pushd=>swap, which I think is more useful. Not to
mention the extra behaviour of the +n stuff.
> the way I interpret AUTO_PUSHD is like the manual says:
> `Make cd act like pushd.'
Hmm. It's a fair cop, guv'nor.
Anthony
*** zshoptions.1.Orig Sun Nov 12 01:09:56 1995
--- zshoptions.1 Sun Nov 12 01:17:36 1995
***************
*** 57,63 ****
then add a trailing slash.
.TP
\fBAUTO_PUSHD\fP (\-\fBN\fP)
! Make \fBcd\fP act like \fBpushd\fP.
.TP
\fBAUTO_REMOVE_SLASH\fP
When the last character resulting from a completion is a slash and the next
--- 57,63 ----
then add a trailing slash.
.TP
\fBAUTO_PUSHD\fP (\-\fBN\fP)
! Make \fBcd\fP push the old directory onto the directory stack.
.TP
\fBAUTO_REMOVE_SLASH\fP
When the last character resulting from a completion is a slash and the next
next reply other threads:[~1995-11-12 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-12 1:51 Heading, Anthony [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-11 21:26 Heading, Anthony
1995-11-12 1:09 ` Danek Duvall
1995-11-10 23:44 Danek Duvall
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=n1395999439.7422@smtpgwprod.ny.jpmorgan.com \
--to=heading_anthony@jpmorgan.com \
--cc=duvall@dhduvall.student.Princeton.EDU \
--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).