From: Paul Ruane <paul.ruane@oniony.com>
To: zsh-users@zsh.org
Subject: Cryptsetup completion
Date: Tue, 2 Jun 2020 17:17:36 +0100 [thread overview]
Message-ID: <CAJZHWOgdLXOKezG59vQNH6yVusyuq8iTiH9mHO1VFuj27HokWQ@mail.gmail.com> (raw)
Hi,
For my own system I have modified the Zsh completion of cryptsetup to
include completion of the hash and cipher based upon those declared
available in /proc/crypto. I thought this might be useful for other
users, too, so I have included my changes below for your
consideration.
11,12c11,12
< '(-c --cipher)'{-c+,--cipher=}'[set cipher]:cipher specification' \
< '(-h --hash)'{-h+,--hash=}'[hash algorithm]:hash algorithm' \
---
> '(-c --cipher)'{-c+,--cipher=}'[set cipher]:cipher specification:_ciphers' \
> '(-h --hash)'{-h+,--hash=}'[hash algorithm]:hash algorithm:_hashes' \
157a158,183
>
> _ciphers() {
> typeset -a cipher_list
> local line
>
> _call_program grep 'grep "^\(name\|type\)\s\+:" /proc/crypto | grep -B1 "^type\s\+:\s\+cipher" | grep "^name\s\+:" | cut -d ":" -f 2 | uniq | sed "s/^ //"' | \
> while read -A line
> do
> cipher_list+=($line[1])
> done
>
> _describe -t ciphers 'cipher' cipher_list "$@"
> }
>
> _hashes() {
> typeset -a hash_list
> local line
>
> _call_program grep 'grep "^\(name\|type\)\s\+:" /proc/crypto | grep -B1 "^type\s\+:\s\+shash" | grep "^name\s\+:" | cut -d ":" -f 2 | uniq | sed "s/^ //"' | \
> while read -A line
> do
> hash_list+=($line[1])
> done
>
> _describe -t hashes 'hash' hash_list "$@"
> }
Paul
next reply other threads:[~2020-06-02 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 16:17 Paul Ruane [this message]
2020-06-03 0:03 ` Mikael Magnusson
2020-06-03 0:55 ` Daniel Shahaf
2020-06-03 11:19 ` Paul Ruane
2020-06-03 12:52 ` Paul Ruane
2020-06-04 2:27 ` Daniel Shahaf
2020-06-04 11:50 ` Oliver Kiddle
2020-06-05 1:55 ` Daniel Shahaf
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=CAJZHWOgdLXOKezG59vQNH6yVusyuq8iTiH9mHO1VFuj27HokWQ@mail.gmail.com \
--to=paul.ruane@oniony.com \
--cc=zsh-users@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).