From: Lucas De Marchi <lucas.demarchi@profusion.mobi>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 4/5] client: Display command even with no description
Date: Tue, 18 Jun 2013 17:13:46 -0300 [thread overview]
Message-ID: <1371586427-7909-4-git-send-email-lucas.demarchi@profusion.mobi> (raw)
In-Reply-To: <1371586427-7909-1-git-send-email-lucas.demarchi@profusion.mobi>
From: Lucas De Marchi <lucas.demarchi@intel.com>
Having no description doesn't mean it's not an available command. So add
command to the output of "help" command, even if it has no description.
---
client/main.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/client/main.c b/client/main.c
index b0a66d8..54af807 100644
--- a/client/main.c
+++ b/client/main.c
@@ -1182,10 +1182,9 @@ static void rl_handler(char *input)
printf("Available commands:\n");
for (i = 0; cmd_table[i].cmd; i++) {
- if (cmd_table[i].desc)
- printf("\t%s %s\t%s\n", cmd_table[i].cmd,
+ printf("\t%s %s\t%s\n", cmd_table[i].cmd,
cmd_table[i].arg ? : " ",
- cmd_table[i].desc);
+ cmd_table[i].desc ? : "");
}
done:
--
1.8.3.1
next prev parent reply other threads:[~2013-06-18 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 20:13 [PATCH BlueZ 1/5] build-sys: Don't build gdbus several times Lucas De Marchi
2013-06-18 20:13 ` [PATCH BlueZ 2/5] gitignore: Add missing tools Lucas De Marchi
2013-06-18 20:13 ` [PATCH BlueZ 3/5] adapter: Remove never used parameter Lucas De Marchi
2013-06-18 20:13 ` Lucas De Marchi [this message]
2013-06-19 5:08 ` [PATCH BlueZ 4/5] client: Display command even with no description Marcel Holtmann
2013-06-19 9:08 ` Johan Hedberg
2013-06-19 10:31 ` Marcel Holtmann
2013-06-19 13:40 ` Lucas De Marchi
2013-06-19 14:54 ` Marcel Holtmann
2013-06-19 15:02 ` Lucas De Marchi
2013-06-18 20:13 ` [PATCH BlueZ 5/5] client: prettify help table Lucas De Marchi
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=1371586427-7909-4-git-send-email-lucas.demarchi@profusion.mobi \
--to=lucas.demarchi@profusion.mobi \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).