From: Istvan Sebestyen <istvan@chains.ch>
To: zsh-workers@sunsite.dk
Subject: Completion for `sub-options'
Date: Sat, 19 Apr 2003 18:39:56 +0200 [thread overview]
Message-ID: <20030419163956.GA25361@chains.ch> (raw)
Hello there!
I began to write a zsh completion for a little httpd. I saw then, that it isn't as easy as i thought, because the program hasn't regular options, it has `sub-options', too. The example would be:
zsh% program --errordoc 404=/var/www/foobar.html
First it should make the completion for the error code, what is trivial to make (401, 404, etc...). The second thing, it should put a `=' after the error-code completion and then look for _files -g '*.(html|htm|php|etc...)'.
I looked into several completions of programs that have such options, too (i.e. like mount), but i couldn't make it work. If someone can give me an easy solution for this problem, I would be very thankful.
Thanks,
Istvan Sebestyen
next reply other threads:[~2003-04-19 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 16:39 Istvan Sebestyen [this message]
2003-04-21 9:03 ` Oliver Kiddle
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=20030419163956.GA25361@chains.ch \
--to=istvan@chains.ch \
--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).