zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Zsh list <zsh-workers@sunsite.dk>
Subject: Re: file completion of ~user/... stats wrong directory
Date: Fri, 10 Jul 2009 10:07:21 +0100	[thread overview]
Message-ID: <20090710100721.56b0874c@news01> (raw)
In-Reply-To: <19030.11925.370937.608524@gargle.gargle.HOWL>

On Thu, 9 Jul 2009 13:53:25 -0400
Greg Klanderman <gak@klanderman.net> wrote:
> Looking at _path_files, I'm guessing it has something to do with
> setting prepaths=( '' ) in the logic dealing with ~ prefixed strings.
> But I don't understand what prepaths is supposed to be doing.  It
> worries me a bit that it is set to that same value in a number of
> other cases.  Maybe it should be setting prepaths=() instead?

prepaths comes from the -W option (see the zparseopts call), which is used
when you want the file matcher to behave as if there was a path
prefix---for example, to complete folders in your mail directory, you might
use "-W ~/Mail".

I think the reason it's not an empty array is that matches are eventually
generated in a loop over all -W paths.  If there are none, we still want to
execute that loop once, but with an empty prepath (at line 340):

for prepath in "$prepaths[@]"; do

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


  reply	other threads:[~2009-07-10  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 17:53 Greg Klanderman
2009-07-10  9:07 ` Peter Stephenson [this message]
2009-07-10 14:06   ` Greg Klanderman
2009-07-10 14:21     ` Peter Stephenson
2009-09-09  4:32       ` Greg Klanderman
2009-09-10 15:07         ` Greg Klanderman
2009-09-10 15:47           ` Bart Schaefer
2009-09-10 15:56             ` Greg Klanderman
2009-09-13 16:52               ` Greg Klanderman
2009-09-15  0:41                 ` Greg Klanderman

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=20090710100721.56b0874c@news01 \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.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).