From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Pattern matching with _files vs command line
Date: Mon, 12 Sep 2016 08:18:01 -0700 [thread overview]
Message-ID: <160912081802.ZM24135@torch.brasslantern.com> (raw)
In-Reply-To: <c4add754-9ff4-370e-1fc5-0df30b4319e8@redhat.com>
On Sep 12, 7:30am, Marko Myllynen wrote:
}
} On 2016-09-10 05:40, Bart Schaefer wrote:
} > On Sep 9, 8:39am, Marko Myllynen wrote:
} > }
} > } _wanted files expl file _files -g '*(-FM)' && ret=0
} >
} > # People prefer to have directories shown on first try as default.
} > # Even if the calling function didn't use -/.
} >
} > zstyle :completion::complete:foo:: file-patterns '%p:globbed-files'
}
} Thanks, this did the trick!
}
} > zstyle :completion::complete:foo:: tag-order globbed-files -
}
} This, however, doesn't seem to work: with or without the former this
} stops completion for foo altogether.
Yes, that's connected to this:
} > HOWEVER, you've actually broken things with your glob pattern. Adding
} > the (M) flag means that the generated completions end with a "/"
If you fix the glob pattern to remove the (M) qualifier, then tag-order
works (at least for me). If you leave the (M) in there, tag-order is
broken. I don't really understand why this is the case; it seems to
have something to do with whether the string passed to "compadd" really
does match a file name (which it won't when the "/" is appended).
next prev parent reply other threads:[~2016-09-12 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 5:39 Marko Myllynen
2016-09-10 2:40 ` Bart Schaefer
[not found] ` <20160911094221.GA18467@fujitsu.shahaf.local2>
2016-09-11 16:18 ` 39093 erases variant with slashes (was: Re: Pattern matching with _files vs command line) Bart Schaefer
2016-09-12 4:30 ` Pattern matching with _files vs command line Marko Myllynen
2016-09-12 15:18 ` Bart Schaefer [this message]
2016-09-12 15:34 ` Marko Myllynen
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=160912081802.ZM24135@torch.brasslantern.com \
--to=schaefer@brasslantern.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).