This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] candidates for ambiguous command in upper case
- From: Simon Marchi <simon dot marchi at polymtl dot ca>
- To: Jerome Guitton <guitton at adacore dot com>
- Cc: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches at sourceware dot org
- Date: Tue, 10 Jan 2017 10:28:35 -0500
- Subject: Re: [RFA] candidates for ambiguous command in upper case
- Authentication-results: sourceware.org; auth=none
- References: <1484058324-5368-1-git-send-email-guitton@adacore.com> <20170110150731.GH9518@E107787-LIN> <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"?