unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: 14790@debbugs.gnu.org
Subject: bug#14790: An issue building Emacs (trunk) manual
Date: Fri, 05 Jul 2013 14:15:08 +0300	[thread overview]
Message-ID: <83a9m1z29v.fsf@gnu.org> (raw)
In-Reply-To: <51D5D5AB.2030005@alice.it>

> Date: Thu, 04 Jul 2013 22:06:03 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: bug-emacs <bug-gnu-emacs@gnu.org>
> 
> Underfull \hbox (badness 10000) in paragraph at lines 328--336
> []@textrm To ei-ther en-able or dis-able Which Func-tion mode, use the 
> com-mand
>   @texttt M-x
> [225] [226] [227] [228] [229] [230] [231] [232] [233] [234] [235] [236]
> [237] [238] [239]) (/work/emacs/doc/emacs/building.texi Chapter 24
> [240] [241] [242]
> Underfull \hbox (badness 10000) in paragraph at lines 243--248
> []@textrm To parse mes-sages from the com-piler, Com-pi-la-tion mode 
> uses the v
> ari-able

"Underfull \hbox" means that there's too few characters to typeset a
line of text without making it ugly.  TeX tries to fill lines, but
when the Texinfo sources requests a fixed-width typeface, such as with
names of variables and functions, it cannot do that.

The solution is to rearrange text around the problematic part.  I
agree with Glenn that doing this now is a waste of effort.

Bottom line: ignore those errors.  ("Overfull boxes", OTOH, are more
serious.)

> As you see, they aren't fatal error but until a few day ago they didn't 
> appear and, as I wrote, they appear only with my patch for A4+open 
> chapter on odd pages.

As the Texinfo sources change, these issues can appear and disappear.
It's normal.  Likewise, they can appear with one paper size and not
the other.





  parent reply	other threads:[~2013-07-05 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 16:43 bug#14790: An issue building Emacs (trunk) manual Angelo Graziosi
2013-07-04 18:12 ` Eli Zaretskii
2013-07-04 20:06   ` Angelo Graziosi
2013-07-04 23:28     ` Glenn Morris
2013-07-04 23:38       ` Angelo Graziosi
2013-07-05  6:34         ` Eli Zaretskii
2013-07-05 11:15     ` Eli Zaretskii [this message]
2013-07-05 11:40       ` Angelo Graziosi

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83a9m1z29v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14790@debbugs.gnu.org \
    --cc=angelo.graziosi@alice.it \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).