zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: mkkwong@lucent.com
Cc: Zsh users <zsh-users@sunsite.auc.dk>
Subject: Re: some directory changing tools to share
Date: Tue, 07 Mar 2000 11:06:38 +0000	[thread overview]
Message-ID: <38C4E2BE.AF06B2F7@u.genie.co.uk> (raw)
In-Reply-To: <200003062114.PAA01448@w-kwong.ih.lucent.com>

mkkwong@lucent.com wrote:
>                 case $_j in
>                         .) dirname=$dirname/..
>                                 continue ;;
>                         ..) dirname=$dirname/../..
>                                 continue ;;
>                         ...) dirname=$dirname/../../..
>                                 continue ;;

This reminds me of a useful feature of 4DOS (a shareware command.com
replacement which I used to use) and I think also for shared drives in
Netware. It allowed series of dots to refer to parent directories beyond
the parent. So, ... refers to the parent of the parent, .... to the
parent of that etc. When I first moved to UNIX, I defined a series of
aliases - cd...=cd ../.. etc although I don't seem to be in the habit of
using them anymore. I also realise that I could use alias -g
'...'='../..' but this only works on single words.

Would it be possible to add an option which extends the zsh filename
generation to expand ... to ../.., .... to ../../.. etc. Would this
conflict with any of the existing globbing system? The only problem I
can foresee is that to refer to a directory named '...' it would be
necessary to quote atleast one of the dots.

Any thoughts?

Oliver Kiddle


  parent reply	other threads:[~2000-03-07 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-06 21:14 mkkwong
2000-03-07  0:32 ` Zefram
2000-03-07  7:36   ` Andrej Borsenkow
2000-03-07 15:33   ` mkkwong
2000-03-07 11:06 ` Oliver Kiddle [this message]
2000-03-07 17:46   ` Bart Schaefer

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=38C4E2BE.AF06B2F7@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --cc=mkkwong@lucent.com \
    --cc=zsh-users@sunsite.auc.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).