From: "percy tiglao" <prtiglao@gmail.com>
Subject: Re: Minor documentation layout flaws
Date: Mon, 28 Aug 2006 19:10:47 -0400 [thread overview]
Message-ID: <aec19dbb0608281610g6a0a48cej483bbfc9672f092d@mail.gmail.com> (raw)
In-Reply-To: <87hczw7cmn.fsf@zip.com.au>
On 8/28/06, Kevin Ryde <user42@zip.com.au> wrote:
> "percy tiglao" <prtiglao@gmail.com> writes:
> >
> > overfull hboxes
>
> If tex would report them in a form that you could step through it'd be
> possible to fix the worst ones.
Actually; it does.
After you do texi2dvi, all the overful hboxes are in "guile.log" (assuming
you did "texi2dvi guile.texi")
The bigger the number (ex: overful hbox: 500pt) the worse it is.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-08-28 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 17:31 Minor documentation layout flaws percy tiglao
2006-08-28 21:51 ` Kevin Ryde
2006-08-28 23:10 ` percy tiglao [this message]
2006-08-29 22:16 ` Neil Jerram
2006-09-02 2:31 ` percy tiglao
2006-09-04 7:02 ` Ludovic Courtès
2006-09-07 20:48 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aec19dbb0608281610g6a0a48cej483bbfc9672f092d@mail.gmail.com \
--to=prtiglao@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).