Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: File-I/O patch, Documentation
Date: Tue, 26 Nov 2002 06:07:00 -0000	[thread overview]
Message-ID: <20021126150645.A6174@cygbert.vinschen.de> (raw)
In-Reply-To: <2110-Mon25Nov2002210126+0200-eliz@is.elta.co.il>

On Mon, Nov 25, 2002 at 09:01:26PM +0300, Eli Zaretskii wrote:
> > From: Corinna Vinschen <vinschen@redhat.com>
> > > > +@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


  reply	other threads:[~2002-11-26 14:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  1:04 Corinna Vinschen
2002-11-21  1:22 ` Corinna Vinschen
2002-11-23  3:04   ` Eli Zaretskii
2002-11-23  3:02 ` Eli Zaretskii
2002-11-23  8:12   ` Andrew Cagney
2002-11-25  2:52   ` Corinna Vinschen
2002-11-25 11:01     ` Eli Zaretskii
2002-11-26  6:07       ` Corinna Vinschen [this message]
2002-11-26 10:02         ` Eli Zaretskii
2002-11-27  9:08           ` Corinna Vinschen
2003-02-26 23:20 ` Andrew Cagney
2003-02-27  8:37   ` Corinna Vinschen
2003-02-27 23:05     ` Andrew Cagney
2003-02-28  8:33       ` Corinna Vinschen
2003-02-28 15:25         ` Daniel Jacobowitz
2003-02-28 15:49           ` Corinna Vinschen
2003-02-28 16:37             ` Daniel Jacobowitz
2003-02-28 15:27         ` Andrew Cagney
2003-02-28 15:47           ` Corinna Vinschen
2003-03-02  3:03             ` Andrew Cagney
2003-03-03 12:12               ` Corinna Vinschen
2003-03-04 18:53                 ` Andrew Cagney
2003-03-04 19:46                   ` Eli Zaretskii
2003-03-06 21:19                     ` Andrew Cagney
2003-03-06 21:26                 ` Andrew Cagney
2003-03-07 14:29                   ` Corinna Vinschen
2003-03-07 14:55                     ` Andrew Cagney
2003-03-01 12:36     ` Eli Zaretskii
2003-03-01 15:43       ` 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=20021126150645.A6174@cygbert.vinschen.de \
    --to=vinschen@redhat.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