Re: another bug: zsh_directory_name

[Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>]

Oliver Kiddle wrote:
> Out of interest what are people using this for. It seems like a nice
> idea, but I've yet to think of an actual use that can't be done with a
> normal named directory. Transformations on the current $PWD seem to be
> one logical option - ${PWD/src/include} for instance. Or an easier syntax
> for (../)#

I'm using it for simplified hierarchies.  ~[p] means my normal Perforce
client, ~[p1] my alternative one, so ~[p:u] is
/home/pws/perforce/uwb/main/fw/src while ~[p1:u] is
/home/pws/perforcel1/uwb/main/fw/src, and so on.  In other words, I can
replace multiple chunks in the directory path very briefly; I could only
do that with static names by naming every possible combination.

See my previous post for how I'm doing completion on these.

-- 
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/