From: Glenn Morris <rgm@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Cannot generate web manuals
Date: Sun, 29 Dec 2013 15:13:51 -0500 [thread overview]
Message-ID: <wppofe7pc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAF+z6EtDHu3-Fn60D_Dn7ENNu82VARBK0e5t6j5U6fC6tOqcQ@mail.gmail.com> (Xue Fuqiao's message of "Sun, 29 Dec 2013 12:04:59 +0800")
Xue Fuqiao wrote:
> with `make-manuals' in admin/admin.el, but met an error. I've attached
> the backtrace.
>
> I invoked this command without using prefix argument (which means to
> generate all kinds of manuals: HTML, PDF, and PostScript). The error
> occurred when generating the "emacs-node" manual (which is the first
> step).
It works fine for me with makeinfo 4.13. Perhaps something is different
in makeinfo 5.
> Should I file a bug report?
Depends if you want someone to fix it at some point, or if you just want
a chat.
> BTW perhaps we should use something like `make-progress-reporter' to
> report the progress of this function, since it'll take a long time.
Why bother? It's obvious when it's working.
> I'll also start to work on generating PDF and PostScript versions of
> doc/misc manuals as requested by Jambunathan K[fn:1] later.
I would not bother if I were you. To date we intentionally only provide
the main manuals in non-html formats. It is a pain to keep multiple
formats up-to-date, for little benefit IMO.
> I also have a question here: `manual-html-mono' does not generate the
> manual for lispref. How was
> http://www.gnu.org/software/emacs/manual/html_mono/elisp.html generated?
Using M-x make-manuals. I don't know why you think it doesn't make
html_mono/elisp.html.
next prev parent reply other threads:[~2013-12-29 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 4:04 Cannot generate web manuals Xue Fuqiao
2013-12-29 5:53 ` Thien-Thi Nguyen
2013-12-29 15:43 ` Eli Zaretskii
2013-12-29 20:13 ` Glenn Morris [this message]
2013-12-29 23:32 ` Xue Fuqiao
2013-12-30 1:26 ` Glenn Morris
2013-12-30 3:47 ` Stephen J. Turnbull
2013-12-30 14:28 ` Xue Fuqiao
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=wppofe7pc.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=xfq.free@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.
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.