From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix 'Undefined command' error message
Date: Tue, 22 Nov 2005 05:38:00 -0000 [thread overview]
Message-ID: <ufyppy7uo.fsf@gnu.org> (raw)
In-Reply-To: <4382072A.1010402@st.com> (message from Andrew STUBBS on Mon, 21 Nov 2005 17:43:06 +0000)
> Date: Mon, 21 Nov 2005 17:43:06 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb-patches@sources.redhat.com
>
> Eli Zaretskii wrote:
> > I'd prefer to have the same characters allowed in all CLI commands.
> > Any other way would be very confusing to users.
> >
> > Thanks for the other clarifications. I think we should at least add
> > comments that explain the respective characters.
>
> I have moved all three instances of this code in to one function, added
> comments, removed the pointless '*p' and allowed the TUI characters all
> the time.
>
> The XDB characters clash with existing GDB commands so I have left those
> disabled unless in XDB mode. Specifically commands such as 'x/i' fail
> because the command there is actually only 'x'. Obviously this does not
> affect commands such as 'x /i'.
Thanks, I'm happy with this patch.
prev parent reply other threads:[~2005-11-21 22:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 18:11 Andrew STUBBS
2005-11-16 4:52 ` Eli Zaretskii
2005-11-16 14:56 ` Andrew STUBBS
2005-11-16 20:19 ` Eli Zaretskii
2005-11-16 23:28 ` Daniel Jacobowitz
2005-11-17 0:10 ` Eli Zaretskii
2005-11-22 2:17 ` Andrew STUBBS
2005-11-22 2:31 ` Andreas Schwab
2005-11-23 18:58 ` Andrew STUBBS
2005-11-23 19:19 ` Eli Zaretskii
2005-11-23 21:07 ` Andrew STUBBS
2005-11-24 4:33 ` Daniel Jacobowitz
2005-11-24 17:29 ` Eli Zaretskii
2005-11-24 18:11 ` Daniel Jacobowitz
2005-11-24 20:31 ` Eli Zaretskii
2005-11-24 22:37 ` Andrew STUBBS
2005-11-24 23:57 ` Eli Zaretskii
2005-11-24 10:34 ` Eli Zaretskii
2005-11-22 5:38 ` Eli Zaretskii [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=ufyppy7uo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sources.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