From: John Beppu <beppu@ax9.org>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Rough Draft of Article on Writing Completion Functions
Date: Thu, 11 Apr 2002 12:46:34 -0700 [thread overview]
Message-ID: <20020411194634.GA27390@Ax9.org> (raw)
In-Reply-To: <7906.1018000673@csr.com>
[ date ] 2002/04/05 | Friday | 10:57 AM
[ author ] Peter Stephenson <pws@csr.com>
> I deliberately didn't write a whole real-world completion function
> because there are already so many to look at,
I think you should have done it, anyway. I'll explain
why in a second.
> > The great tragedy of Zsh is that they actually made it very easy to
> > write completion functions, but you'd never know it by just
> > reading the documentation.
>
> Hmm... how much simpler than
>
> _foo() { compadd Yan Tan Tethera; }
> compdef _foo foo
>
> do I need to get? This is the sort of hint I need from the puzzled.
Beginners don't need "simple". They need "practical".
Would you tell some chump off the street:
This is how to jab;
This is a hook;
This is an uppercut;
Now go fight Mike Tyson.
Clearly, this guy is going to be unprepared for the task at hand.
That's why a long practical example that explains the task of writing a
completion function from start to finish would have been helpful.
> I suggest you mention that you need zsh 4.0.x as a matter of priority,
> regardless of space limitations, or some people are going to get
> confused
OK.
next prev parent reply other threads:[~2002-04-11 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020404234932.GA27875@Ax9.org>
2002-04-05 7:05 ` Sven Wischnowsky
2002-04-11 19:48 ` John Beppu
[not found] ` <7906.1018000673@csr.com>
2002-04-11 19:46 ` John Beppu [this message]
[not found] <E16tQka-0005p0-00@bimbo.logica.co.uk>
2002-04-05 19:28 ` John Beppu
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=20020411194634.GA27390@Ax9.org \
--to=beppu@ax9.org \
--cc=zsh-workers@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).