zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@math.gatech.edu
Subject: Re: bug 3.1.5 symlinks & cd
Date: Wed, 18 Nov 1998 14:06:40 +0100	[thread overview]
Message-ID: <9811181306.AA62590@ibmth.df.unipi.it> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Wed, 18 Nov 1998 10:09:34 NFT." <199811180909.KAA14049@beta.informatik.hu-berlin.de>

Sven Wischnowsky wrote:
> So the question is: do you think that this is enough (probably with
> some more work on the function) or should we build this into the shell?

Isn't the problem only with ../ ?  -/ and the rest happily follow
symlinks, it's only when going up there's a problem.  In that case, it
would be OK to use -/ most of the time and only have a special
function when there's a ../ in the string so far.  As the only case
where you would normally use this is ../ at the start (although I've
been known to use $PWD/.. when I needed an absolut path), I should
have thought a shell function for this one case would have been quite
good enough.  ../../ etc. is a complication, but one a function could
still easily handle. (Unless I've missed some other potential
problem.)

Presumably it will one day become possible to replace the (../)# with
a truncated version of $PWD, then reapply -/ using the -W option to
compctl to generate the completions you want.  Then the script
solution ought to become pretty painless.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56100 Pisa, Italy


  reply	other threads:[~1998-11-18 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-18  9:09 Sven Wischnowsky
1998-11-18 13:06 ` Peter Stephenson [this message]
1998-11-18 19:25 ` Bart Schaefer
1998-11-18 22:41 ` Phil Pennock
  -- strict thread matches above, loose matches on Subject: below --
1998-11-18 13:41 Sven Wischnowsky
1998-11-16  9:28 Sven Wischnowsky
1998-11-13 21:19 Phil Pennock
1998-11-14  5:48 ` Bart Schaefer
1998-11-15  3:01   ` Phil Pennock

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=9811181306.AA62590@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --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).