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 20:26:19 -0500 [thread overview]
Message-ID: <vqha9rrux0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAF+z6Ens3ye3NPhrstTmhCV1XHsKjE0FAcQRw0PHYYP1MW=qg@mail.gmail.com> (Xue Fuqiao's message of "Mon, 30 Dec 2013 07:32:24 +0800")
Xue Fuqiao wrote:
>> 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'?
Of course you _can_ do that, I'm saying it's pointless.
Does any distribution package the pdf versions of those files?
Is there anyone who really wants the pdf version and does not have
access to TeX?
I guarantee you that if you only do some, someone will complain about
the ones you did not do. So you'll have to do them all. And update all
formats, at every release.
> But why does `manual-html-mono' and `manual-html-node' only include
> (by "makeinfo -I") `doc/emacs' and `doc/misc'?
Because those are the only directories from which we need to pick up
included files (emacsver.texi and texinfo.tex).
next prev parent reply other threads:[~2013-12-30 1:26 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
2013-12-30 1:26 ` Glenn Morris [this message]
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
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=vqha9rrux0.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 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).