From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Add completer for skip numbers
Date: Mon, 12 Nov 2018 15:40:00 -0000 [thread overview]
Message-ID: <b829dad584eec887c3a596df1e5b6c7f@polymtl.ca> (raw)
In-Reply-To: <d072f76f-7f8f-1b21-3192-3ebe98117361@redhat.com>
On 2018-11-12 07:41, Pedro Alves wrote:
> On 11/11/2018 04:54 PM, Simon Marchi wrote:
>> Add completer to various commands that accept skip numbers:
>>
>> - skip enable
>> - skip disable
>> - skip delete
>> - info skip
>>
>> These commands also accept ranges, the completer works for that but is
>> not very smart. It will suggest invalid ranges, for example when
>> doing
>> "2-<TAB>" it will suggest "1", which would not result in a valid
>> range.
>> Also, it will keep suggesting when doing "1-2-<TAB>", even though it's
>> an invalid syntax.
>>
>> A future idea would be to make a re-usable and well-tested completer
>> for
>> numbers and ranges. I think it could at least be re-used for
>> breakpoint
>> and thread numbers (for example with the "enable breakpoints"
>> command).
>>
>> gdb/ChangeLog:
>>
>> * skip.c (complete_skip_number): New function.
>> (_initialize_step_skip): Add completers to some skip commands.
>>
>> gdb/testsuite/ChangeLog:
>>
>> * gdb.base/skip.exp: Add standard_testfile. Add "skip delete"
>> completer tests.
>
> OK.
>
> Thanks,
> Pedro Alves
Thanks, pushed.
Simon
prev parent reply other threads:[~2018-11-12 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 16:54 Simon Marchi
2018-11-12 12:41 ` Pedro Alves
2018-11-12 15:40 ` Simon Marchi [this message]
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=b829dad584eec887c3a596df1e5b6c7f@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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