From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: PATCH: new _losetup
Date: Wed, 28 Aug 2002 18:20:31 +0100 [thread overview]
Message-ID: <E17k6Ua-0003BC-00@bimbo.logica.co.uk> (raw)
new completion for losetup.
Does anyone mind if I move _valgrind and _modutils to
Completion/Linux/Command?
On the subject of _modutils, shouldn't there be some sort of '*:...'
_arguments spec in it so that it covers the normal case when you just
load a module.
Oliver
Index: Completion/Linux/Command/_losetup
===================================================================
RCS file: Completion/Linux/Command/_losetup
diff -N Completion/Linux/Command/_losetup
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ Completion/Linux/Command/_losetup 28 Aug 2002 16:54:24 -0000
@@ -0,0 +1,14 @@
+#compdef losetup
+
+local cyphers
+cyphers=( /proc/crypto/cipher/*(N:t) )
+cyphers="${cyphers[@]%-*}"
+
+_arguments -S \
+ '(- 2)'{--delete,--detach,-d}'[detach from specified loop device]' \
+ '(-d --delete --detach -e --encryption)'{-e,--encryption}"+[enable encryption]:cypher:( $cyphers )" \
+ '(-d --delete --detach -o --offset)'{-o,--offset}'+[specify data start is offset]:offset (bytes)' \
+ '(-d --delete --detach -p --pass-fd)'{-p,--pass-fd}'+[read passphrase from specified file descriptor]:file descriptor:_file_descriptors' \
+ '(-d --delete --detach -k --keybits)'{-k,--keybits}'+[set the number of bits to use in key]:key size:(64 128 160 192 256)' \
+ '1:device:_files -g loop\*' \
+ '(-d --delete --detach)2:file:_files'
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
reply other threads:[~2002-08-28 17: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=E17k6Ua-0003BC-00@bimbo.logica.co.uk \
--to=okiddle@yahoo.co.uk \
--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).