diff options
author | Pedro Alves <palves@redhat.com> | 2019-06-13 00:06:52 +0100 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2019-06-13 00:10:03 +0100 |
commit | 597bf39df91c9a2e27cf1966dd4c942ac645ae33 (patch) | |
tree | 0096227f6cd886277d5149a9fb2d8076dccef48c /gdb/cli/cli-utils.c | |
parent | 48c410fb70fe09c036e27092880db687e5c2fb0b (diff) | |
download | gdb-597bf39df91c9a2e27cf1966dd4c942ac645ae33.zip gdb-597bf39df91c9a2e27cf1966dd4c942ac645ae33.tar.gz gdb-597bf39df91c9a2e27cf1966dd4c942ac645ae33.tar.bz2 |
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:
2019-06-13 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.
Diffstat (limited to 'gdb/cli/cli-utils.c')
0 files changed, 0 insertions, 0 deletions