From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
schwab@suse.de, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix 'Undefined command' error message
Date: Thu, 24 Nov 2005 04:33:00 -0000 [thread overview]
Message-ID: <20051123191940.GA20765@nevyn.them.org> (raw)
In-Reply-To: <4384BD74.1060600@st.com>
On Wed, Nov 23, 2005 at 07:05:24PM +0000, Andrew STUBBS wrote:
> Eli Zaretskii wrote:
> >What TUI commands use these problematic characters, and how does TUI
> >avoid the problems pointed out by Andreas?
>
> I don't know what uses '$', but the other three, '>', '<' and '+', are
> commands in their own right and are used the move the source window
> right, left and up through the file. '-' moves down. There may be other
> commands I don't know about.
>
> The TUI does *not* avoid the problems pointed out by Andreas. 'u+1' must
> be written 'u +1'. The latter syntax seems more correct to me in any
> case - the '+' is part of the operand, not the command. That said, many
> people are probably used to using the command like Andreas.
I had no idea this was possible (or what it did, until I tried it)... I
wouldn't cry about breaking it if there was any benefit.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-23 19:19 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 [this message]
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
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=20051123191940.GA20765@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@suse.de \
/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