From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: Add matchspec for foo/bar branch names in git completion
Date: Sun, 17 May 2015 23:42:57 +0000 [thread overview]
Message-ID: <20150517234257.GG2214@tarsus.local2> (raw)
In-Reply-To: <150516211642.ZM4541@torch.brasslantern.com>
Bart Schaefer wrote on Sat, May 16, 2015 at 21:16:42 -0700:
> On May 16, 10:53pm, Daniel Shahaf wrote:
> }
> } Other ideas?
>
> I just looked again at your original patch, and I *think* you'll get what
> you want if you simply change all 'r:|=*' to be 'r:|=**'.
Works, thanks!
next prev parent reply other threads:[~2015-05-17 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 14:37 Daniel Shahaf
2015-05-14 17:35 ` Bart Schaefer
2015-05-16 22:53 ` Daniel Shahaf
2015-05-17 4:16 ` Bart Schaefer
2015-05-17 23:42 ` Daniel Shahaf [this message]
2015-05-19 1:52 ` Daniel Shahaf
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=20150517234257.GG2214@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).