From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Cc: syphdias@gmail.com
Subject: Re: [PATCH 2/2] run-help: add run-help-btrfs
Date: Wed, 9 Dec 2020 18:14:28 +0900 [thread overview]
Message-ID: <A3B50AD4-3FFB-4AD7-9111-6A6E66318ECE@kba.biglobe.ne.jp> (raw)
In-Reply-To: <20181227152444.31608-2-me@rmz.io>
Another patch we missed.
> 2018/12/28 0:24, Samir Benmendil <me@rmz.io> wrote:
>
> --- /dev/null
> +++ b/Functions/Misc/run-help-btrfs
(snip)
> + (i*) man btrfs-image ;;
> + (m*) man btrfs-map-logical ;;
These two are not subcommands of btrfs.
> + (q*) man btrfs-qgroup ;;
> + (q*) man btrfs-quota ;;
These two must be distinguished.
diff --git a/Functions/Misc/run-help-btrfs b/Functions/Misc/run-help-btrfs
new file mode 100644
index 000000000..0dc1dabcb
--- /dev/null
+++ b/Functions/Misc/run-help-btrfs
@@ -0,0 +1,22 @@
+while [[ $# != 0 && $1 == -* ]]; do
+ shift
+done
+
+case $1 in
+ (b*) man btrfs-balance ;;
+ (c*) man btrfs-check ;;
+ (d*) man btrfs-device ;;
+ (f*) man btrfs-filesystem ;;
+ (i*) man btrfs-inspect-internal ;;
+ (p*) man btrfs-property ;;
+ (qg*) man btrfs-qgroup ;;
+ (qu*) man btrfs-quota ;;
+ (rec*) man btrfs-receive ;;
+ (rep*) man btrfs-replace ;;
+ (resc*) man btrfs-rescue ;;
+ (rest*) man btrfs-restore ;;
+ (sc*) man btrfs-scrub ;;
+ (se*) man btrfs-send ;;
+ (su*) man btrfs-subvolume ;;
+ (*) man btrfs ;;
+esac
-----
Jun
next prev parent reply other threads:[~2020-12-09 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 15:24 [PATCH 1/2] run-help: chain run-help-sudo to call run-help on the next argument Samir Benmendil
2018-12-27 15:24 ` [PATCH 2/2] run-help: add run-help-btrfs Samir Benmendil
2020-12-09 9:14 ` Jun T [this message]
2020-12-09 15:51 ` Christian K
2020-12-11 6:08 ` Jun T
2020-12-09 9:05 ` [PATCH 1/2] run-help: chain run-help-sudo to call run-help on the next argument Jun T
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=A3B50AD4-3FFB-4AD7-9111-6A6E66318ECE@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=syphdias@gmail.com \
--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).