From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@zsh.org>
Subject: PATCH: fix yafc completion
Date: Thu, 13 Oct 2016 11:15:11 +0200 [thread overview]
Message-ID: <8932.1476350111@hydra.kiddle.eu> (raw)
A spurious space before compdef prevents the yafc completion from being
picked up. Aside from that, this just tweaks a few minor things.
Oliver
diff --git a/Completion/Unix/Command/_yafc b/Completion/Unix/Command/_yafc
index df9623b..edc7c41 100644
--- a/Completion/Unix/Command/_yafc
+++ b/Completion/Unix/Command/_yafc
@@ -1,28 +1,28 @@
-# compdef yafc
+#compdef yafc
_yafc() {
- local arguments
- arguments=(
+ local arguments
+ arguments=(
'(--anon -a)'{--anon,-a}'[try an anonymous login]'
'(--debug -d)'{--debug,-d}'[print all messages to/from server]'
'(--dump-rc -D)'{--dump-rc,-D}'[print the default configuration file]'
- '(--mechanism -m)'{--mechanism=-,-m}'[specify a security mechanism]:security mechanism:(krb4, krb5, none)'
- '(--norc -n)'{--norc,-n}'[do not read the users configuration file]'
- '(--noproxy -p)'{--noproxy,-p}'[do not connect via the proxy]'
- '(--quiet -q)'{--quiet,-q}'[do not print the welcome message]'
+ '(--mechanism -m)'{--mechanism=-,-m}'[specify a security mechanism]:security mechanism:(krb4 krb5 none)'
+ '(--norc -n)'{--norc,-n}"[don't read the users configuration file]"
+ '(--noproxy -p)'{--noproxy,-p}"[don't connect via the proxy]"
+ '(--quiet -q)'{--quiet,-q}"[don't print the welcome message]"
'(--rcfile -r)'{--rcfile=-,-r}'[specify a configuration file]:configuration file:_files'
'(--trace -t)'{--trace=-,-t-}'[specify a trace file]:trace file:_files'
- '(--noauto -u)'{--noauto,-u}'[do not login automagically]'
+ '(--noauto -u)'{--noauto,-u}"[don't login automatically]"
'(--noalias -U)'{--noalias,-U}'[as --noauto, but bookmark aliases is disabled]'
'(--verbose -v)'{--verbose,-v}'[print all responses received]'
- '(--wait -w)'{--wait,-w=}'[specify a waiting time between connection attempts]:wait time: '
+ '(--wait -w)'{--wait,-w=}'[specify a waiting time between connection attempts]:wait time (seconds)'
'(--workdir -W)'{--workdir=,-W+}'[use a different working directory]:working directory:_directories'
- '(--version -V)'{--version,-V}'[print version information]'
- '(--help -h)'{--help,-h}'[print a short help description]'
+ '(- *)'{--version,-V}'[print version information]'
+ '(- *)'{--help,-h}'[print a short help description]'
'*:address:_yafc_address'
- )
+ )
- _arguments -S -s $arguments
+ _arguments -S -s $arguments
}
(( $+functions[_yafc_bookmarks] )) ||
reply other threads:[~2016-10-13 9:21 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=8932.1476350111@hydra.kiddle.eu \
--to=okiddle@yahoo.co.uk \
--cc=zsh-workers@zsh.org \
/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).