Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Make use of gdb::options for info variabels|functions|args|locals
Date: Thu, 11 Jul 2019 16:05:00 -0000	[thread overview]
Message-ID: <e4463ff0-3eca-77c7-1ec3-3a2bbd569c63@redhat.com> (raw)
In-Reply-To: <20190711155305.GO23204@embecosm.com>

On 7/11/19 4:53 PM, Andrew Burgess wrote:
> * Pedro Alves <palves@redhat.com> [2019-07-11 14:36:23 +0100]:
> 
>> On 7/11/19 2:20 PM, Andrew Burgess wrote:
>>> Additional use of the gdb::options framework.
>>>
>>> --
>>>
>>> Andrew Burgess (2):
>>>   gdb: Allow quoting around string options in the gdb::option framework
>>
>> Ahaha, that didn't take long.  Thanks for doing this.  LGTM.
>>
>>>   gdb: Make use of gdb::option framework for some info commands
>>
>> This LGTM to me too, but, I was surprised to find this doesn't add
>> completers at the same time?
> 
> Something like this, maybe?

_Exactly_ like that.  Perfect.

So far, I've listed this sort of improvement under
"Completion improvements" in NEWS.  I think you lists these commands
there too, and it'd be an obvious change.

> +
> +  const char *word = advance_to_expression_complete_word_point (tracker, text);
> +  symbol_completer (ignore, tracker, text, word);
> +  return;

Redundant "return".

Thanks,
Pedro Alves


  reply	other threads:[~2019-07-11 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 13:21 Andrew Burgess
2019-07-11 13:21 ` [PATCH 2/2] gdb: Make use of gdb::option framework for some info commands Andrew Burgess
2019-07-11 13:21 ` [PATCH 1/2] gdb: Allow quoting around string options in the gdb::option framework Andrew Burgess
2019-07-11 16:17   ` Tom Tromey
2019-07-11 19:21     ` Andrew Burgess
2019-07-11 13:36 ` [PATCH 0/2] Make use of gdb::options for info variabels|functions|args|locals Pedro Alves
2019-07-11 15:53   ` Andrew Burgess
2019-07-11 16:05     ` Pedro Alves [this message]
2019-07-11 19:21       ` Andrew Burgess
2019-07-11 16:08     ` Tom Tromey

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=e4463ff0-3eca-77c7-1ec3-3a2bbd569c63@redhat.com \
    --to=palves@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.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