From: reckoner <reckoner@gmail.com>
To: zsh-users@zsh.org
Subject: Re: How to change order of completions?
Date: Wed, 03 Apr 2013 14:39:57 -0700 [thread overview]
Message-ID: <515CA1AD.8000108@gmail.com> (raw)
> On Apr 1, 7:27am, reckoner wrote:
> }
> } file.tex , file.dvi, file.log, file.aux
> }
> } and I would like to complete on the *.tex files before any other
file.
> See here: http://zsh.sourceforge.net/Guide/zshguide06.html#l159
> So something like
> zstyle ':completion:*:vi(|m):*' file-patterns \
> '*.tex:tex-files' '*.(c|cpp|c++|h|py):src-files' '*:all-files'
This works great except when I have
% vi () { gvim $* }
as a user-defined function.
% vi<TAB>
doesn't work but
% vim<TAB>
works as expected.
next reply other threads:[~2013-04-03 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 21:39 reckoner [this message]
2013-04-03 22:35 ` Bart Schaefer
2013-04-04 1:09 ` reckoner
-- strict thread matches above, loose matches on Subject: below --
2013-04-01 14:27 reckoner
2013-04-01 15:04 ` Bart Schaefer
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=515CA1AD.8000108@gmail.com \
--to=reckoner@gmail.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).