all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Cannot generate web manuals
Date: Mon, 30 Dec 2013 07:32:24 +0800	[thread overview]
Message-ID: <CAAF+z6Ens3ye3NPhrstTmhCV1XHsKjE0FAcQRw0PHYYP1MW=qg@mail.gmail.com> (raw)
In-Reply-To: <wppofe7pc.fsf@fencepost.gnu.org>

On Mon, Dec 30, 2013 at 4:13 AM, Glenn Morris <rgm@gnu.org> wrote:
> 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.

Done as #16295.

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

This way the user (maintainer) can estimate remaining time and clearly
see that Emacs is busy working, not hung.  Anyway, this is only my opinion.

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

Why?  Can't we just use the same method used by emacs/lispref/eintr for
`(manual-misc-manuals)' and just press `M-x make-manuals'?

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

You're right.  But why does `manual-html-mono' and `manual-html-node'
only include (by "makeinfo -I") `doc/emacs' and `doc/misc'?  I did't see
lispref there.

-- 
http://www.gnu.org/software/emacs/



  reply	other threads:[~2013-12-29 23:32 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
2013-12-29 23:32   ` Xue Fuqiao [this message]
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='CAAF+z6Ens3ye3NPhrstTmhCV1XHsKjE0FAcQRw0PHYYP1MW=qg@mail.gmail.com' \
    --to=xfq.free@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.