From: Brian Ford <ford@vss.fsi.com>
To: gdb-patches@sources.redhat.com
Subject: cli-decode.c and tui_active
Date: Fri, 14 Feb 2003 19:56:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.44.0302141349000.21272-200000@eos> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 387 bytes --]
The following trivial patch is needed to build cvs gdb on Cygwin on
anywhere TUI is not defined:
2003-02-14 Brian Ford <ford@vss.fsi.com>
* cli/cli-decode.c (lookup_cmd_composition) [TUI]: Properly
conditionalize tui_active test.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
[-- Attachment #2: Type: TEXT/PLAIN, Size: 1072 bytes --]
Index: cli-decode.c
===================================================================
RCS file: /cvs/src/src/gdb/cli/cli-decode.c,v
retrieving revision 1.29
diff -u -p -u -p -r1.29 cli-decode.c
--- cli-decode.c 14 Feb 2003 13:58:06 -0000 1.29
+++ cli-decode.c 14 Feb 2003 19:55:11 -0000
@@ -927,8 +927,10 @@ lookup_cmd_1 (char **text, struct cmd_li
`tui_version'. */
for (p = *text;
*p && (isalnum (*p) || *p == '-' || *p == '_' ||
+#if defined(TUI)
(tui_active &&
(*p == '+' || *p == '<' || *p == '>' || *p == '$')) ||
+#endif
(xdb_commands && (*p == '!' || *p == '/' || *p == '?')));
p++)
;
@@ -1299,8 +1301,10 @@ lookup_cmd_composition (char *text,
`tui_version'. */
for (p = text;
*p && (isalnum (*p) || *p == '-' || *p == '_' ||
+#if defined(TUI)
(tui_active &&
(*p == '+' || *p == '<' || *p == '>' || *p == '$')) ||
+#endif
(xdb_commands && (*p == '!' || *p == '/' || *p == '?')));
p++)
;
next reply other threads:[~2003-02-14 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 19:56 Brian Ford [this message]
2003-02-14 20:37 ` Elena Zannoni
2003-02-19 23:35 ` Andrew Cagney
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=Pine.GSO.4.44.0302141349000.21272-200000@eos \
--to=ford@vss.fsi.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