From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>
Subject: Re: can't build gnus.info
Date: Tue, 11 Sep 2001 17:34:03 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0109111731360.1620-100000@lie.extundo.com> (raw)
In-Reply-To: <m366apwyj2.fsf@multivac.cwru.edu>
On Tue, 11 Sep 2001, Paul Jarc wrote:
> With a CVS checkout from just now:
> if test "xmakeinfo" != "xno" ; then \
> makeinfo -I . -o gnus gnus.texi; \
> else \
> emacs -batch -q -no-site-file -l ./infohack.el -f batch-makeinfo gnus.texi; \
> fi
> Making info file `gnus' from `gnus.texi'.
> gnus.texi:5077: itemize requires an argument: the formatter for @item.
> makeinfo: Removing output file `gnus' due to errors; use --force to preserve.
> make[1]: *** [gnus] Error 2
> make[1]: Leaving directory `/fs/lvm/mount/home/prj/src/gnus/texi'
>
> I have no knowlegde of texinfo, but it looks like line 5077 should be
> "@itemize @bullet" instead of "@itemize".
I changed it, thanks.
(Altough I don't get the error. I'm using makeinfo 4.0.)
prev parent reply other threads:[~2001-09-11 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 15:13 Paul Jarc
2001-09-11 15:34 ` Simon Josefsson [this message]
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=Pine.LNX.4.33.0109111731360.1620-100000@lie.extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.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.
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).