From: Phil Pennock <phil.pennock@globnix.org>
To: zsh-users@sunsite.dk
Subject: Re: Completion of dirs confused over cursor position
Date: Thu, 9 Jan 2003 16:06:46 +0000 [thread overview]
Message-ID: <20030109160645.GA22637@globnix.org> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5CE@MOWD019A>
On 2003-01-09 at 18:02 +0300, Borzenkov Andrey wrote:
> function _foo {
> _files -W /some/directory
> }
> compadd _foo commandname
>
> does it work?
No:
compadd: can only be called from completion function
However, that's looking much simpler than anything in the manual pages
or the examples I looked at in the distributed completions. :^) I was
getting lost in functions calling functions calling functions
maintaining various levels of state, with reference man-pages and no
tutorial.
Is there a tutorial somewhere which I've missed? The manual pages are
some of the most daunting I've seen. I do read manual-pages, but
looking at these I can't get a mental handle on the frameword and what
fits where, to get started.
> And doing it automatically:
>
> echo > ~/functions/_foo << EOF
> #compadd commandname
> _files -W /some/directory
> EOF
That general structure I had (although I suspect that you meant cat,
since echo doesn't use its stdin). And the supplied versions use
"#compdef". If I use "#compadd", it's not auto-loaded.
> fpath=($fpath ~/functions)
> compinit
And that I had.
> the last part obviously goes into .zshrc or whatever. Try running
> compinstall as well.
Yup, tried that.
Okay, logging in again, forcing a rebuild of .zcompdump (after changing
to "#compdef", it now works. :^)
Thanks,
-Phil
next prev parent reply other threads:[~2003-01-09 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 19:46 Phil Pennock
2003-01-09 10:42 ` Peter Stephenson
2003-01-09 14:51 ` Phil Pennock
2003-01-09 15:02 ` Borzenkov Andrey
2003-01-09 16:06 ` Phil Pennock [this message]
2003-01-09 16:01 ` Borzenkov Andrey
2003-01-09 18:35 ` Bart Schaefer
2003-01-10 13:58 ` Phil Pennock
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=20030109160645.GA22637@globnix.org \
--to=phil.pennock@globnix.org \
--cc=zsh-users@sunsite.dk \
/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).