From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11730 invoked by alias); 10 Jun 2006 07:51:27 -0000 Received: (qmail 11717 invoked by uid 22791); 10 Jun 2006 07:51:26 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 10 Jun 2006 07:51:23 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-164-172.inter.net.il [80.230.164.172]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id EVQ89300 (AUTH halo1); Sat, 10 Jun 2006 10:51:18 +0300 (IDT) Date: Sat, 10 Jun 2006 07:51:00 -0000 Message-Id: From: Eli Zaretskii To: Nick Roberts CC: gdb-patches@sources.redhat.com In-reply-to: <17546.915.125070.943811@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 10 Jun 2006 11:26:11 +1200) Subject: Re: [PATCH] MI Doco Reply-to: Eli Zaretskii References: <17535.33986.598009.914783@kahikatea.snap.net.nz> <17536.4472.263731.425097@kahikatea.snap.net.nz> <17538.8607.697546.427486@kahikatea.snap.net.nz> <17546.915.125070.943811@kahikatea.snap.net.nz> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00121.txt.bz2 > From: Nick Roberts > Date: Sat, 10 Jun 2006 11:26:11 +1200 > Cc: gdb-patches@sources.redhat.com > > > > ! However, CLI commands that use sequences of commands such @code{source}, > > > ! @code{commands} will not work > > > > I don't understand from this text what will not work. (Please enclose > > input that would be typed by user in @kbd, btw.) Do you mean if I > > type "source, commands", it will not work? Or do you mean something > > else? > > > > Also, you are missing "as" after "such", I think. > > I'm not sure what I meant either. I committed this part, as is, inadvertantly > but I've tried to address it as part of the patch below. Sorry. Maybe you meant `commands', `while', etc.--those commands that prompt for the body which ends with `end'? Then `source' is not part of the endangered commands. > > > ! target. This is only present when GDB's event loop > > > > Please use @value{GDBN} instead a literal "GDB". > > I left this unchanged after reading the ensuing discussion. The discussion was about "(gdb)" vs "(@value{GDBP})". "GDB" should still be converted to "@value{GDBN}", as that has nothing to do with "set prompt". But I see you did remove literal "GDB". > just note that all I did here was move existing text. Yes, I know. Thanks. > In the patch below, I'm trying to group the commands in a similar (but not > identical) fashion to the CLI commands in the main part of the manual. To > that end, I would like to have the node ordering: > > * GDB/MI Breakpoint Commands:: > * GDB/MI Program Context:: > * GDB/MI Thread Commands:: > * GDB/MI Program Execution:: > * GDB/MI Stack Manipulation:: > * GDB/MI Variable Objects:: > * GDB/MI Data Manipulation:: > * GDB/MI Tracepoint Commands:: > * GDB/MI Symbol Query:: > * GDB/MI File Commands:: > * GDB/MI Target Manipulation:: > * GDB/MI Miscellaneous Commands:: > > I've not done this in the patch because it would make it totally unreadable, > of course. Is such an ordering acceptable? Yes.