zsh-workers
 help / color / mirror / code / Atom feed
From: Greg Klanderman <gak@klanderman.net>
To: zsh-workers@sunsite.dk
Subject: Re: file completion of ~user/... stats wrong directory
Date: Fri, 10 Jul 2009 10:06:20 -0400	[thread overview]
Message-ID: <m31vooljj7.fsf@klanderman.net> (raw)
In-Reply-To: <20090710100721.56b0874c@news01> (Peter Stephenson's message of "Fri, 10 Jul 2009 10:07:21 +0100")

>>>>> Peter Stephenson <pws@csr.com> writes:

> 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".

Right, I'd kinda surmised it was something like that.

> 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

So do you agree it's a bug that it's stat-ing the path with the ~user/
stripped off, effectively then relative to the current directory?

So, if it needs to go through that loop at least once, then maybe when
'prepath' (singular) is '' it should be prepending any stuff that got
stripped off the front back on?  Guess I'll have to grovel through
there and try to make sense of what's going on...

Greg


  reply	other threads:[~2009-07-10 14:06 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
2009-07-10 14:06   ` Greg Klanderman [this message]
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=m31vooljj7.fsf@klanderman.net \
    --to=gak@klanderman.net \
    --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).