From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jerome Guitton <guitton@adacore.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] candidates for ambiguous command in upper case
Date: Tue, 10 Jan 2017 15:28:00 -0000 [thread overview]
Message-ID: <ee9212f7e0041953919f60df47699efa@polymtl.ca> (raw)
In-Reply-To: <20170110151944.GD27546@adacore.com>
On 2017-01-10 10:19, Jerome Guitton wrote:
> Yao Qi (qiyaoltc@gmail.com):
>
>> IMO, there is nothing wrong. There is no command starts from "EX".
>
> This is a bit weird to accept upper-case EXEC-FIL then... isn't it?
>
> (gdb) exec-fil
> No executable file now.
> (gdb) EXEC-FIL
> No executable file now.
I agree that if GDB accepts commands in upper case, the ambiguous
command message should work accordingly. The message as it is, with an
empty list, doesn't make sense.
I also noticed that tab completion was case sensitive, should that be
fixed as well?
For example,
(gdb) inf<tab><tab>
shows "inferior info", but
(gdb) INF<tab><tab>
shows nothing. Should it show "inferior info", or "INFERIOR INFO"?
next prev parent reply other threads:[~2017-01-10 15:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1484058324-5368-1-git-send-email-guitton@adacore.com>
2017-01-10 15:07 ` Yao Qi
2017-01-10 15:19 ` Jerome Guitton
2017-01-10 15:28 ` Simon Marchi [this message]
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
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=ee9212f7e0041953919f60df47699efa@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
--cc=qiyaoltc@gmail.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