From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7074 invoked by alias); 26 Nov 2002 14:07:05 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7067 invoked from network); 26 Nov 2002 14:07:03 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 26 Nov 2002 14:07:03 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gAQDgdP18658 for ; Tue, 26 Nov 2002 08:42:39 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gAQE71s31076 for ; Tue, 26 Nov 2002 09:07:02 -0500 Received: from cygbert.vinschen.de (vpn50-11.rdu.redhat.com [172.16.50.11]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id gAQE70M17988 for ; Tue, 26 Nov 2002 06:07:00 -0800 Received: (from corinna@localhost) by cygbert.vinschen.de (8.11.6/8.9.3/Linux sendmail 8.9.3) id gAQE6ju06617 for gdb-patches@sources.redhat.com; Tue, 26 Nov 2002 15:06:45 +0100 Date: Tue, 26 Nov 2002 06:07:00 -0000 From: Corinna Vinschen To: gdb-patches@sources.redhat.com Subject: Re: [RFA]: File-I/O patch, Documentation Message-ID: <20021126150645.A6174@cygbert.vinschen.de> Reply-To: gdb-patches@sources.redhat.com Mail-Followup-To: gdb-patches@sources.redhat.com References: <20021121100443.U24928@cygbert.vinschen.de> <7458-Sat23Nov2002130204+0200-eliz@is.elta.co.il> <20021125115158.C27250@cygbert.vinschen.de> <2110-Mon25Nov2002210126+0200-eliz@is.elta.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2110-Mon25Nov2002210126+0200-eliz@is.elta.co.il> User-Agent: Mutt/1.3.22.1i X-SW-Source: 2002-11/txt/msg00643.txt.bz2 On Mon, Nov 25, 2002 at 09:01:26PM +0300, Eli Zaretskii wrote: > > From: Corinna Vinschen > > > > +@smallexample > > > > +(gdb) continue > > > ^^^^^ > > > This should be @value{GDBP}... > > > > Should it? That's the GDB prompt. It's used plain text in other > > examples in the text as well so I assumed that being correct here. > > Well, gdbint.texinfo indeed didn't use @value{GDBN} and @value{GDBP} > until very recently, unlike gdb.texinfo. I think the decision was to > use them in both manuals, but I might be mistaken. Andrew? Aaandrew? > > No, the effect is different: > > > > `F'RETCODE`,'ERRNO`,'CTRL-C FLAG`;'CALL SPECIFIC ATTACHMENT > > > > Your version: > > > > `FRETCODE,ERRNO,CTRL-C FLAG;CALL SPECIFIC ATTACHMENT' > > Well, I think my result is more accurate ;-) Those `' around F and > such are not really there in the packet, right? > > But if you think your result is better, I won't insist. Ok, I will use my version. My reasoning is that in an info reader it's pretty hard to distinguish between the fixed parts like the leading `F' and the variable parts as "retcode". > @smallexample > Synopsis: int open(const char *pathname, int flags); > int open(const char *pathname, int flags, mode_t mode); > > Request: Fopen,pathptr/len,flags,mode > @end smallexample > > @noindent > where @code{flags} is the bitwise or of the following values: > > @table @code > @item O_CREAT > If the file does not exist it will be created. The host > rules apply as far as file ownership and time stamps > are concerned. > > @item O_EXCL > When used with O_CREAT, if the file already exists it is > an error and open() fails. > ... > @end table I like the idea and I'd like to use it. However, there is one problem I don't know how to solve correctly. The "Synopsis", "Request" etc. are unfortunately indented due to the usage of smallexample. I tried using @noindent but that has no influence in a smallexample. Using a @table @samp doesn't work either because it quotes the headlines and ``Synopsis:'' int open ... doesn't look that nice. How can I get the typical typeset for the "Synopsis" etc. paragraphs but without the indenting of smallexample? > Either will do, so in this case it's up to you. Actually, I could > make an argument for having both ;-) Ok, I added two more @cindex. Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:vinschen@redhat.com