Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 07/24] Remove "show" command completers
Date: Fri, 24 May 2019 14:21:00 -0000	[thread overview]
Message-ID: <87tvdkndbd.fsf@redhat.com> (raw)
In-Reply-To: <86392fa6-b345-79a1-1870-d3c0324c968e@redhat.com> (Pedro Alves's	message of "Fri, 24 May 2019 12:25:43 +0100")

On Friday, May 24 2019, Pedro Alves wrote:

> On 5/23/19 8:28 PM, Sergio Durigan Junior wrote:
>> On Wednesday, May 22 2019, Pedro Alves wrote:
>> 
>>> The default command completer is symbol_completer, but it makes no
>>> sense for a "show" command to complete on symbols, or anything else,
>>> really.
>> 
>> Agreed.
>> 
>>> I wonder whether we should instead make the default be no completer.
>>> That seems like a much larger/complicated audit/change, so I'd like to
>>> move forward with this version, as it'll be covered by tests.  I
>>> noticed this because a following patch will add a new
>>> gdb.base/settings.exp testcase that exercises all sorts of details of
>>> settings commands, including completing the show commands, using new
>>> representative "maint test-settings <type or settings command>"
>>> commands.
>> 
>> I'm wondering why you chose to remove call set_cmd_completer on all of
>> the add_setshow_* functions if you could actually have called it once on
>> add_setshow_cmd_full, which is a static function and just used on
>> cli-decode.c anyway.
>
> Wow, how did I miss that?  Much simpler, thanks!
>
> Now that I do this, it stands out what made me look at this code
> originally (which I had forgotten).
>
> It's that the var_string "set" commands complete on symbols, but
> that doesn't make much sense; that's what I first noticed when I
> was writing the gdb.base/settings.exp testcase.  When I fixed that,
> while looking at the code, I realized that the "show" commands shouldn't
> also complete on anything.  And then just copied over the same code to all
> set/show commands, failing to notice that I could do it in
> add_setshow_cmd_full.

Yeah, I noticed you were also setting the completer for some of the
"set" commands as NULL as well :-).

> Here's the updated patch.

Much better, thanks!

FWIW, I'm still reviewing the other patches in the series.  Will let you
know when I have more comments.

> From f4ba132856c870156d145d556c6e77d4cafb60a9 Mon Sep 17 00:00:00 2001
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 22 May 2019 18:52:35 +0100
> Subject: [PATCH 07/24] Remove "show" command completers, "set" command completers
>  for string commands
>
> The default command completer is symbol_completer, but it makes no
> sense for a "show" command to complete on symbols, or anything else,
> really.
>
> I wonder whether we should instead make the default be no completer.
> That seems like a much larger/complicated audit/change, so I'd like to
> move forward with this version, as it'll be covered by tests.  I
> noticed this because a following patch will add a new
> gdb.base/settings.exp testcase that exercises all sorts of details of
> settings commands, including completing the show commands, using new
> representative "maint test-settings <type or settings command>"
> commands.
>
> Also remove the completer for var_string and var_string_noescape
> commands.  No point in completing symbols when GDB is expecting a
> string.
>
> gdb/ChangeLog:
> yyyy-mm-dd  Pedro Alves  <palves@redhat.com>
>
> 	* cli/cli-decode.c (add_setshow_cmd_full): Remove "show"
> 	completer.
> 	(add_setshow_string_cmd, add_setshow_string_noescape_cmd): Remove
> 	"set" completers.
> ---
>  gdb/cli/cli-decode.c | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/cli/cli-decode.c b/gdb/cli/cli-decode.c
> index 72e2a970097..80158593b38 100644
> --- a/gdb/cli/cli-decode.c
> +++ b/gdb/cli/cli-decode.c
> @@ -508,6 +508,9 @@ add_setshow_cmd_full (const char *name,
>  			      full_show_doc, show_list);
>    show->doc_allocated = 1;
>    show->show_value_func = show_func;
> +  /* Disable the default symbol completer.  Doesn't make much sense
> +     for the "show" command to complete on anything.  */
> +  set_cmd_completer (show, nullptr);
>  
>    if (set_result != NULL)
>      *set_result = set;
> @@ -632,11 +635,16 @@ add_setshow_string_cmd (const char *name, enum command_class theclass,
>  			struct cmd_list_element **set_list,
>  			struct cmd_list_element **show_list)
>  {
> +  cmd_list_element *set_cmd;
> +
>    add_setshow_cmd_full (name, theclass, var_string, var,
>  			set_doc, show_doc, help_doc,
>  			set_func, show_func,
>  			set_list, show_list,
> -			NULL, NULL);
> +			&set_cmd, NULL);
> +
> +  /* Disable the default symbol completer.  */
> +  set_cmd_completer (set_cmd, nullptr);
>  }
>  
>  /* Add element named NAME to both the set and show command LISTs (the
> @@ -658,6 +666,10 @@ add_setshow_string_noescape_cmd (const char *name, enum command_class theclass,
>  			set_func, show_func,
>  			set_list, show_list,
>  			&set_cmd, NULL);
> +
> +  /* Disable the default symbol completer.  */
> +  set_cmd_completer (set_cmd, nullptr);
> +
>    return set_cmd;
>  }
>  
> -- 
> 2.14.5

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2019-05-24 14:21 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 20:53 [PATCH 00/24] gdb::option framework, "print -OPT", other cmd options Pedro Alves
2019-05-22 20:53 ` [PATCH 03/24] Fix TID parser bug Pedro Alves
2019-05-22 20:53 ` [PATCH 07/24] Remove "show" command completers Pedro Alves
2019-05-23 19:28   ` Sergio Durigan Junior
2019-05-24 11:25     ` Pedro Alves
2019-05-24 14:21       ` Sergio Durigan Junior [this message]
2019-05-22 20:53 ` [PATCH 08/24] gdb.base/settings.exp: Fix comment typo Pedro Alves
2019-05-24 11:40   ` Pedro Alves
2019-05-22 20:53 ` [PATCH 18/24] lib/completion-support.exp: Add test_gdb_completion_offers_commands Pedro Alves
2019-05-22 20:53 ` [PATCH 11/24] number_or_range_parser::get_number, don't treat "1 -" as a range Pedro Alves
2019-05-22 20:53 ` [PATCH 04/24] Make check_for_argument skip whitespace after arg itself Pedro Alves
2019-05-22 20:53 ` [PATCH 19/24] Introduce complete_command Pedro Alves
2019-05-22 20:53 ` [PATCH 15/24] Introduce rename_cmd Pedro Alves
2019-05-25 19:58   ` Philippe Waroquiers
2019-05-29 16:03     ` Pedro Alves
2019-05-29 18:30       ` Pedro Alves
2019-05-30 10:22         ` Philippe Waroquiers
2019-05-30 20:01           ` Pedro Alves
2019-05-22 20:54 ` [PATCH 22/24] Make "thread apply" use the gdb::option framework Pedro Alves
2019-05-25 20:24   ` Philippe Waroquiers
2019-05-29 15:38     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 10/24] boolean/auto-boolean commands, make "o" ambiguous Pedro Alves
2019-05-22 20:54 ` [PATCH 20/24] Make "frame apply" support -OPT options Pedro Alves
2019-05-25 20:12   ` Philippe Waroquiers
2019-05-29 15:13     ` Pedro Alves
2019-05-29 15:25       ` Pedro Alves
2019-05-22 20:54 ` [PATCH 14/24] Migrate rest of compile commands to new options framework Pedro Alves
2019-05-22 20:54 ` [PATCH 01/24] Fix latent bug in custom word point completion handling Pedro Alves
2019-05-22 20:54 ` [PATCH 02/24] Fix latent bug with custom word point completers Pedro Alves
2019-05-22 20:54 ` [PATCH 12/24] Introduce generic command options framework Pedro Alves
2019-05-25  7:43   ` Philippe Waroquiers
2019-05-25 10:31     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 21/24] "thread apply 1 -- -" vs "frame apply level 0 -- -" Pedro Alves
2019-05-22 20:54 ` [PATCH 09/24] New set/show testing framework (gdb.base/settings.exp) Pedro Alves
2019-05-23  4:15   ` Eli Zaretskii
2019-05-22 20:54 ` [PATCH 05/24] Allow "unlimited" abbreviations Pedro Alves
2019-05-22 20:54 ` [PATCH 06/24] Fix "set enum-command value garbage" Pedro Alves
2019-05-23 19:13   ` Sergio Durigan Junior
2019-05-24 11:39     ` Pedro Alves
2019-05-22 20:58 ` [PATCH 13/24] Make "print" and "compile print" support -OPT options Pedro Alves
2019-05-24 19:49   ` Sergio Durigan Junior
2019-05-25 10:10     ` Pedro Alves
2019-05-25 10:37       ` Andreas Schwab
2019-05-22 20:58 ` [PATCH 16/24] Make "backtrace" " Pedro Alves
2019-05-22 21:00 ` [PATCH 17/24] "backtrace full/no-filters/hide" completer Pedro Alves
2019-05-22 21:00 ` [PATCH 24/24] NEWS and manual changes for command options changes Pedro Alves
2019-05-23  4:31   ` Eli Zaretskii
2019-05-23 15:01     ` Pedro Alves
2019-05-23 15:07       ` Eli Zaretskii
2019-05-23 15:31         ` Pedro Alves
2019-05-25 20:40   ` Philippe Waroquiers
2019-05-29 16:03     ` Pedro Alves
2019-05-22 21:03 ` [PATCH 23/24] Delete parse_flags/parse_flags_qcs Pedro Alves
2019-05-22 21:46 ` [PATCH 00/24] gdb::option framework, "print -OPT", other cmd options Pedro Alves
2019-05-24 19:58 ` Sergio Durigan Junior

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=87tvdkndbd.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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