Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add ``Maintenance Commands'' appendix
Date: Wed, 16 Jan 2002 23:36:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020117093451.13091D-100000@is> (raw)
In-Reply-To: <3C45E31B.8010403@cygnus.com>


On Wed, 16 Jan 2002, Andrew Cagney wrote:

> Attached is a revised patch.  It moves the ``maint info breakpoints'' 
> and adds a reference.  it appears to work with texinfo 4.0*, texi2html 
> (1.64) and pdftex.  How does it look?

Looks fine.

> Regarding a switch to ``makeinfo --html'' I think I'll put it on hold. 
> I gave it a quick trial but tripped up on two points: I couldn't figure 
> out where exactly it was putting the generated files (it wanted a 
> gdb.html/ directory but put only index.html in it)

That's a bug in 4.0d; fixed in the next pretest that should be
available shortly (I'm told by the Texinfo maintainer).

> I found the 
> generated pages too fine grained (down to a section not chapter).

It splits by nodes, so what's important is where are the @node
directives, not @chapter or @section.  I think for a Web-based manual,
a node is the right split point, as chapters can be very large.


  reply	other threads:[~2002-01-17  7:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 21:35 Andrew Cagney
2002-01-14 23:57 ` Eli Zaretskii
2002-01-15 12:19   ` Andrew Cagney
2002-01-15 12:27     ` Michael Snyder
2002-01-15 21:57       ` Andrew Cagney
2002-01-15 22:11     ` Eli Zaretskii
2002-01-15 22:26       ` Andrew Cagney
2002-01-15 22:52         ` Eli Zaretskii
2002-01-16  7:41           ` Andrew Cagney
2002-01-16  8:33             ` Eli Zaretskii
2002-01-16 12:31               ` Andrew Cagney
2002-01-16 23:36                 ` Eli Zaretskii [this message]
2002-01-17 15:04                   ` 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.SUN.3.91.1020117093451.13091D-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.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