all messages for Emacs-related lists mirrored at yhetil.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: Thu, 04 Jul 2013 21:12:17 +0300	[thread overview]
Message-ID: <83hagayz26.fsf@gnu.org> (raw)
In-Reply-To: <51D5A618.3060407@alice.it>

> Date: Thu, 04 Jul 2013 18:43:04 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> 
> Now, say after r. 113247 (a few days ago), building the PDF produces 
> some "harmless" errors (the PDF is created) which one doesn't like to see:
> 
> $ make emacs.pdf 2>&1 | tee ~/work/emacs_pdf_a4.log
> 
> $ grep -i error ~/work/emacs_pdf_a4.log
> @textrm (@texttt compilation-next-error[]@textrm ) and @texttt M-p[] 
> @textrm (@
> texttt compilation-previous-error[]@textrm ) to move to
> @textrm (@texttt compilation-next-error[]@textrm ) and @texttt M-p[] 
> @textrm (@
> texttt compilation-previous-error[]@textrm ) to move to
> @textrm (@texttt compilation-next-error[]@textrm ) and @texttt M-p[] 
> @textrm (@
> texttt compilation-previous-error[]@textrm ) to move to
> @textrm (@texttt compilation-next-error[]@textrm ) and @texttt M-p[] 
> @textrm (@
> texttt compilation-previous-error[]@textrm ) to move to

Please show the full error messages.  They identify the source lines
and also give additional information about the problems.





  reply	other threads:[~2013-07-04 18:12 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 [this message]
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

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=83hagayz26.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 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.