Zsh Mailing List Archive
Messages sorted by:
Re: Second form of cd.
- X-seq: zsh-users 2305
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxxxxxx
- Subject: Re: Second form of cd.
- Date: Wed, 14 Apr 1999 09:02:25 -0700
- In-reply-to: <19990413153219.A20809@xxxxxxxxxxxxxxxxx>
- In-reply-to: <19990413170738.A9872@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <19990413153219.A20809@xxxxxxxxxxxxxxxxx> <19990413170738.A9872@xxxxxxxxxxxxxxxxxxxx>
On Apr 13, 3:32pm, Larry P. Schrof wrote:
} Subject: Second form of cd.
} I am wondering if this an intentional feature or a bug. I am running
It's the intended behavior. Interpret that as you will.
} When you type 'cd <old> <new>' on the command line, zsh replaces
} only the FIRST occurance of <old> in the directory. I've actually run
} into situations where <old> occurs more than once in $PWD, and I'd
} like <new> to replace this second occurance of old.
The way I usually deal with this is to disambiguate the replacement
string somehow. E.g. suppose the two directories are
"cd src build" attempts to change to ~/build/package/src/subdir/, which
doesn't exist. So instead I type something like
cd src/s build/s
to force the match on the correct substring.
} I am requesting that <new> replace ALL occurances of <old> in $PWD, not
} just the first one.
That would, in many cases, be equally wrong. The best solution for this
On Apr 13, 5:07pm, Sweth Chandramouli wrote:
} Subject: Re: Second form of cd.
} along the same lines, the ^old^new form of history substitution
} replaces just the first instance of old. perhaps a flag of some sort
} (cd -g, maybe, for cd, and ^^old^new for history substitution?) could be
} added to indicate that global replacement should occur?
What's wrong with !!:gs/old/new ? Horrors, four whole extra characters?
Bart Schaefer Brass Lantern Enterprises
Messages sorted by: