From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Subject: PATCH: _knock
Date: Sun, 6 Mar 2005 22:02:55 -0500 [thread overview]
Message-ID: <20050307030255.GA15037@scowler.net> (raw)
I'm putting this in Unix even though there appears to be a Win32
knock.exe.
Index: Completion/Unix/Command/_knock
===================================================================
RCS file: Completion/Unix/Command/_knock
diff -N Completion/Unix/Command/_knock
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ Completion/Unix/Command/_knock 7 Mar 2005 03:02:23 -0000
@@ -0,0 +1,9 @@
+#compdef knock
+
+_arguments \
+ '(-u --udp)'{-u,--udp}'[UDP mode]' \
+ '(-v --verbose)'{-v,--verbose}'[verbose]' \
+ '(-V --version -h --help -u --udp -v --verbose)'{-V,--version}'[display version]' \
+ '(-h --help -u --udp -v --verbose -V --version)'{-h,--help}'[help]' \
+ '1:host:_hosts' \
+ '*:port:_ports'
reply other threads:[~2005-03-07 3:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050307030255.GA15037@scowler.net \
--to=clint@zsh.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).