From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27656 invoked by alias); 11 Jan 2014 23:41:08 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18321 Received: (qmail 19355 invoked from network); 11 Jan 2014 23:41:02 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140111154103.ZM14769@torch.brasslantern.com> Date: Sat, 11 Jan 2014 15:41:03 -0800 In-reply-to: Comments: In reply to "Keerthan jai.c" "Re: Approximate file path completion for git?" (Jan 11, 5:13pm) References: <140110213433.ZM22191@torch.brasslantern.com> <140110233725.ZM22285@torch.brasslantern.com> <140111095818.ZM14468@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: Approximate file path completion for git? MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Jan 11, 5:13pm, Keerthan jai.c wrote: } } Backing out 31159 and unsetopt nomatch; works for me. However, unsetopt } nullglob breaks it again. Drat, I thought I'd tried this and seen differently. no_nomatch without no_nullglob is a no-op, effectively just backing out 31159 without doing anything in its place. Apparently the only way to get both the prefix completion speed desired by some and the partial completion accuracy desired by others is to try both routes, fastest first, which is likely actually even slower for the accuracy crowd.