From: Jerome Guitton <guitton@adacore.com>
To: Pedro Alves <palves@redhat.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: Thu, 12 Jan 2017 10:18:00 -0000 [thread overview]
Message-ID: <20170112101854.GL27546@adacore.com> (raw)
In-Reply-To: <b65e1ded-a53b-74d1-169b-806da8fc321d@redhat.com>
Pedro Alves (palves@redhat.com):
> I can only guess on original motivation -- maybe to make GDB usable
> with uppercase-only terminals? Those were common at some point in
> the past. I think Linux's terminal subsystem might still have
> support for those. But then symbol searching was not case-insensitive,
> ("set case-sensitive off" support was only added much later), so I
> can't quite imagine how that'd be much usable.
I'm not sure of the original motivation; but I guess that if it has
been there for thirty years it is now considered as the standard
interface by a few users.
In any case, even if we decide to change that, consistency would be
good, at least for CLI; the same policy for casing should apply in all
cases of completion.
Documenting it in the user manual would be good indeed; I'm not sure
where the proper place would be though.
next prev parent reply other threads:[~2017-01-12 10:18 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
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 [this message]
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=20170112101854.GL27546@adacore.com \
--to=guitton@adacore.com \
--cc=gdb-patches@sourceware.org \
--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