From: Boris Egorov <egorov@linux.com>
To: util-linux@vger.kernel.org
Cc: Boris Egorov <egorov@linux.com>
Subject: [PATCH 3/3] bash-completion: remove unused variables [shellcheck]
Date: Tue, 2 Jun 2015 23:59:03 +0600 [thread overview]
Message-ID: <1433267943-2276-4-git-send-email-egorov@linux.com> (raw)
In-Reply-To: <1433267943-2276-1-git-send-email-egorov@linux.com>
Fix shellcheck SC2034 warnings.
Signed-off-by: Boris Egorov <egorov@linux.com>
---
bash-completion/addpart | 2 +-
bash-completion/fsck | 2 +-
bash-completion/fsck.minix | 2 +-
bash-completion/lsblk | 1 -
bash-completion/mkfs | 2 +-
bash-completion/mkfs.bfs | 2 +-
bash-completion/mkfs.minix | 1 -
7 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/bash-completion/addpart b/bash-completion/addpart
index e9ed793..3179639 100644
--- a/bash-completion/addpart
+++ b/bash-completion/addpart
@@ -1,6 +1,6 @@
_addpart_module()
{
- local cur prev
+ local cur
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
case $COMP_CWORD in
diff --git a/bash-completion/fsck b/bash-completion/fsck
index d61b37f..301bb5d 100644
--- a/bash-completion/fsck
+++ b/bash-completion/fsck
@@ -1,6 +1,6 @@
_fsck_module()
{
- local cur prev OPTS DEVS
+ local cur prev OPTS
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
prev="${COMP_WORDS[COMP_CWORD-1]}"
diff --git a/bash-completion/fsck.minix b/bash-completion/fsck.minix
index 4ed5110..b2b2860 100644
--- a/bash-completion/fsck.minix
+++ b/bash-completion/fsck.minix
@@ -1,6 +1,6 @@
_fsck.minix_module()
{
- local cur prev OPTS DEVS
+ local cur prev OPTS
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
prev="${COMP_WORDS[COMP_CWORD-1]}"
diff --git a/bash-completion/lsblk b/bash-completion/lsblk
index 1692dad..e32f371 100644
--- a/bash-completion/lsblk
+++ b/bash-completion/lsblk
@@ -81,7 +81,6 @@ _lsblk_module()
return 0
;;
esac
- local DEVS
COMPREPLY=( $(compgen -W "$($1 -pnro name)" -- $cur) )
return 0
}
diff --git a/bash-completion/mkfs b/bash-completion/mkfs
index 4edc6f0..a278747 100644
--- a/bash-completion/mkfs
+++ b/bash-completion/mkfs
@@ -1,6 +1,6 @@
_mkfs_module()
{
- local cur prev OPTS DEVS
+ local cur prev OPTS
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
prev="${COMP_WORDS[COMP_CWORD-1]}"
diff --git a/bash-completion/mkfs.bfs b/bash-completion/mkfs.bfs
index 1bd67a0..75458bb 100644
--- a/bash-completion/mkfs.bfs
+++ b/bash-completion/mkfs.bfs
@@ -1,6 +1,6 @@
_mkfs.bfs_module()
{
- local cur prev OPTS DEVS
+ local cur prev OPTS
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
prev="${COMP_WORDS[COMP_CWORD-1]}"
diff --git a/bash-completion/mkfs.minix b/bash-completion/mkfs.minix
index c84a237..3a3602e 100644
--- a/bash-completion/mkfs.minix
+++ b/bash-completion/mkfs.minix
@@ -28,7 +28,6 @@ _mkfs.minix_module()
return 0
;;
esac
- local DEVS
COMPREPLY=( $(compgen -W "$(lsblk -pnro name)" -- $cur) )
return 0
}
--
2.1.4
next prev parent reply other threads:[~2015-06-02 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 17:59 [PATCH 0/3] bash-completion: handle comma-separated options, sync with code, cleanup Boris Egorov
2015-06-02 17:59 ` [PATCH 1/3] bash-completion: handle comma-separated options Boris Egorov
2015-06-02 17:59 ` [PATCH 2/3] bash-completion: sync lscpu completion with code Boris Egorov
2015-06-02 17:59 ` Boris Egorov [this message]
2015-06-08 10:20 ` [PATCH 0/3] bash-completion: handle comma-separated options, sync with code, cleanup Karel Zak
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=1433267943-2276-4-git-send-email-egorov@linux.com \
--to=egorov@linux.com \
--cc=util-linux@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox