From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>, Jerome Guitton <guitton@adacore.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
<gdb-patches@sourceware.org>
Subject: Re: [RFA] candidates for ambiguous command in upper case
Date: Tue, 17 Jan 2017 16:29:00 -0000 [thread overview]
Message-ID: <6872438c-e93a-77e8-79a3-c8e1f05aa283@codesourcery.com> (raw)
In-Reply-To: <b8bc5132-1923-8364-160a-aced2723b840@redhat.com>
On 01/16/2017 07:58 PM, Pedro Alves wrote:
> On 01/16/2017 04:32 PM, Jerome Guitton wrote:
>> Pedro Alves (palves@redhat.com):
>>
>>> Dunno, if it doesn't make sense, and nobody uses it, then it's one
>>> less thing to maintain and test.
>>
>> Hard to figure out if someone uses it, I guess. This originally got
>> reported by one of our users as a minor inconsistancy, who also said
>> that he would be OK if gdb commands were case sensitive.
>>
>> The patch that I'm suggesting is fairly simple, but my feeling is that
>> it would be just as easy to remove the feature.
>>
>> I've tested the opposite: making the match case sensitive is a matter
>> of removing 4 characters in cli-decode.c. Not much consequences in the
>> testsuite. "handle sigq" still completes to "handle SIGQUIT".
>>
>> So, what do we want to do?
>> 1. Remove the feature?
>> 2. Improve its consistency?
>> 3. Keep things as is?
>>
>
> I vote #1.
I don't see a problem with #1 as long as we keep it consistent
throughout from now on.
next prev parent reply other threads:[~2017-01-17 16:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:25 Jerome Guitton
2017-01-10 15:07 ` Yao Qi
2017-01-10 15:19 ` Jerome Guitton
2017-01-10 15:28 ` Simon Marchi
2017-01-10 15:40 ` Jerome Guitton
2017-01-10 17:00 ` Pedro Alves
2017-01-11 15:37 ` Jerome Guitton
2017-01-11 17:26 ` Yao Qi
2017-01-11 17:35 ` Luis Machado
2017-01-11 20:24 ` Pedro Alves
2017-01-12 10:18 ` Jerome Guitton
2017-01-12 16:37 ` Pedro Alves
2017-01-16 16:32 ` Jerome Guitton
2017-01-17 1:58 ` Pedro Alves
2017-01-17 16:29 ` Luis Machado [this message]
2017-01-17 16:35 ` Pedro Alves
2017-01-17 16:51 ` Luis Machado
2017-01-17 17:04 ` Pedro Alves
2017-01-17 17:13 ` Luis Machado
2017-01-31 14:39 ` Jerome Guitton
2017-01-31 15:20 ` Pedro Alves
2017-02-08 18:05 ` Jerome Guitton
2017-07-24 21:17 ` Simon Marchi
2017-07-24 21:48 ` [PATCH] define_command: Don't convert command name to lower case Simon Marchi
2017-07-24 21:54 ` Simon Marchi
2017-08-28 21:20 ` Simon Marchi
2017-07-26 12:42 ` Jerome Guitton
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=6872438c-e93a-77e8-79a3-c8e1f05aa283@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=simon.marchi@polymtl.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).