From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Another _path_files bug?
Date: Sun, 13 Feb 2011 17:54:29 +0000 [thread overview]
Message-ID: <20110213175429.1c95243a@pws-pc.ntlworld.com> (raw)
In-Reply-To: <110212142222.ZM2525@torch.brasslantern.com>
On Sat, 12 Feb 2011 14:22:22 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> This works for the test cases I could think of applying, such as putting
> a full path at the front and (separately) where the tail is ambiguous.
I've committed it with some extra comments that are a bit vaguer than
would be ideal.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
prev parent reply other threads:[~2011-02-13 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 16:42 Bart Schaefer
2011-02-10 17:28 ` Bart Schaefer
2011-02-11 20:39 ` Peter Stephenson
2011-02-12 22:22 ` Bart Schaefer
2011-02-12 23:03 ` Bart Schaefer
2011-02-13 17:54 ` Peter Stephenson [this message]
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=20110213175429.1c95243a@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).