From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: texi2html vs texi2any/makeinfo
Date: Thu, 21 May 2015 12:57:16 +0100 [thread overview]
Message-ID: <20150521125716.3b5dc1e5@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <32342C3E-F511-423D-803D-15CCA1C2E41A@kba.biglobe.ne.jp>
On Thu, 21 May 2015 20:13:54 +0900
Jun T. <takimoto-j@kba.biglobe.ne.jp> wrote:
> I will patch configure.ac so that 'texi2any -c TEXI2HTML=1'
> is used if texi2any is found (texi2any is new in texinfo-5),
> and texi2html otherwise. Is this OK?
That sounds like it ought to be OK --- I'll look at the output I get.
pws
next prev parent reply other threads:[~2015-05-21 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 16:55 texi2html vs texi2any Jun T.
2015-05-20 17:53 ` texi2html vs texi2any/makeinfo Axel Beckert
2015-05-21 11:13 ` Jun T.
2015-05-21 11:57 ` Peter Stephenson [this message]
2015-05-21 13:19 ` Axel Beckert
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=20150521125716.3b5dc1e5@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).