zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Directory completion acts as if CHASE_LINKS is set
Date: Sun, 8 Sep 2013 18:51:36 +0100	[thread overview]
Message-ID: <20130908185136.711ad4ca@pws-pc.ntlworld.com> (raw)
In-Reply-To: <130906220300.ZM31578@torch.brasslantern.com>

On Fri, 06 Sep 2013 22:03:00 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 6,  9:09pm, Peter Stephenson wrote:
> } Subject: Re: Directory completion acts as if CHASE_LINKS is set
> }
> } On Thu, 05 Sep 2013 08:31:39 -0700
> } Bart Schaefer <schaefer@brasslantern.com> wrote:
> } > +    # Use cd in a subshell to properly [not] resolve symlinks
> } > +    tmpprefix=$(cd $PREFIX >&/dev/null && print $PWD) ||
> } > +      tmpprefix=$(cd $PREFIX:h >&/dev/null && print $PWD/$PREFIX:t)
> 
> } I also wonder if it would be better only to look at previous
> } directory components, i.e. always take the PREFIX up to the last "/"
> } (and require that there be one) rather than have two cases.
> 
> You'll have to actually write out what you mean here, because I can't
> get it to work for e.g. "cd ../" without having the first case there.

I'm thinking of something like ${PREFIX%/*}.

pws


  reply	other threads:[~2013-09-08 17:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05  1:23 Jan Larres
2013-09-05  2:15 ` Jan Larres
2013-09-05 15:31 ` Bart Schaefer
2013-09-06  1:42   ` Jan Larres
2013-09-06  6:13     ` Bart Schaefer
2013-09-06  6:46       ` Jan Larres
2013-09-06 20:09   ` Peter Stephenson
2013-09-07  5:03     ` Bart Schaefer
2013-09-08 17:51       ` Peter Stephenson [this message]
2013-09-08 21:26         ` Bart Schaefer
2013-09-09  9:59           ` Peter Stephenson
2013-09-10 14:26           ` Bart Schaefer
2013-09-10 22:34             ` Jan Larres

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=20130908185136.711ad4ca@pws-pc.ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /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).