From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Ronan Pigott <rpigott314@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Ronan Pigott <rpigott@berkeley.edu>
Subject: Re: [PATCH BlueZ 1/3] client/main: add help option for available args
Date: Fri, 16 Aug 2019 14:29:13 +0300 [thread overview]
Message-ID: <CABBYNZL-Pbwg=DUW5a0Q+Xo7R7KeCMx4KkPHQ5LEaUZttze_2g@mail.gmail.com> (raw)
In-Reply-To: <20190816074333.24673-2-rpigott@berkeley.edu>
Hi Ronan,
On Fri, Aug 16, 2019 at 10:46 AM Ronan Pigott <rpigott314@gmail.com> wrote:
>
> From: Ronan Pigott <rpigott@berkeley.edu>
Can you a description of what the changes does, perhaps a sample when
uses in some command.
> ---
> client/main.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/client/main.c b/client/main.c
> index 578b3c7c3..0f810901a 100644
> --- a/client/main.c
> +++ b/client/main.c
> @@ -800,6 +800,14 @@ static gboolean parse_argument(int argc, char *argv[], const char **arg_table,
> {
> const char **opt;
>
> + if (!strcmp(argv[1], "help")) {
> + for (opt = arg_table; opt && *opt; opt++) {
> + bt_shell_printf("%s\n", *opt);
> + }
> + bt_shell_noninteractive_quit(EXIT_SUCCESS);
> + return FALSE;
> + }
> +
> if (!strcmp(argv[1], "on") || !strcmp(argv[1], "yes")) {
> *value = TRUE;
> if (option)
> --
> 2.22.1
>
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2019-08-16 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 7:43 [PATCH BlueZ 0/3] Add zsh completions for bluetoothctl Ronan Pigott
2019-08-16 7:43 ` [PATCH BlueZ 1/3] client/main: add help option for available args Ronan Pigott
2019-08-16 11:29 ` Luiz Augusto von Dentz [this message]
2019-08-16 7:43 ` [PATCH BlueZ 2/3] completion: add bluetoothctl zsh completions Ronan Pigott
2019-08-16 11:36 ` Luiz Augusto von Dentz
2019-08-16 7:43 ` [PATCH BlueZ 3/3] build: install " Ronan Pigott
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='CABBYNZL-Pbwg=DUW5a0Q+Xo7R7KeCMx4KkPHQ5LEaUZttze_2g@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rpigott314@gmail.com \
--cc=rpigott@berkeley.edu \
/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).