Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Skipping certain completers -- how?
- X-seq: zsh-workers 14925
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Skipping certain completers -- how?
- Date: Fri, 15 Jun 2001 09:39:53 +0000
- In-reply-to: <200106150707.JAA08344@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200106150707.JAA08344@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Jun 15, 9:07am, Sven Wischnowsky wrote:
}
} There is the -e option to zstyle, of course (and I've added an example
} for the `completer' style with it some time ago -- in the Overview
} section in compsys.yo).
Er, ahem, yes, ah, well ...
That does almost solve the specific cvs example, but it means writing
your own set of tests for what the context is. That is, I want the
restriction to apply to the subcommand name, and it'd be OK if it also
applied to any options either of cvs or of the subcommand, but I don't
want to restrict the completers used for the actual file arguments.
} I have been thinking about something similar to [a control function.]
} The problem is to decide which conditions we should make it be
} conditional upon, there are so many things people might want to test.
There, zstyle -e can be used to even better effect. The "hard part" has
been done by computing the context; the rest of the conditions can then
be included in the value of the style.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author