all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14790@debbugs.gnu.org
Subject: bug#14790: An issue building Emacs (trunk) manual
Date: Fri, 05 Jul 2013 13:40:56 +0200	[thread overview]
Message-ID: <51D6B0C8.7030306@alice.it> (raw)
In-Reply-To: <83a9m1z29v.fsf@gnu.org>

Il 05/07/2013 13.15, Eli Zaretskii ha scritto:
>> 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
>

Eli,
> "Underfull \hbox" means that there's too few characters to typeset a


I know what "Underfull \hbox" means (almost every LaTeX document 
produces that), my observations were for the other "error" messages 
(those catched by grep) that until rev. 113247 didn't appear..

Anyway, no problems. As I wrote, they aren't "fatal"...


Ciao,
  Angelo.





      reply	other threads:[~2013-07-05 11:40 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
2013-07-05 11:40       ` Angelo Graziosi [this message]

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=51D6B0C8.7030306@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=14790@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.