unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: karl@freefriends.org, emacs-devel@gnu.org, storm@cua.dk
Subject: Re: makeinfo 4.7
Date: Thu, 31 Aug 2006 01:59:08 +0300	[thread overview]
Message-ID: <87y7t5x4ur.fsf@jurta.org> (raw)
In-Reply-To: <u1wqyczr1.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 30 Aug 2006 12:57:22 +0300")

>> Just like we prefer that users upgrade to the latest version of emacs
>> (to avoid spending time on bug reports for older versions), I'm sure
>> the maintainers of makeinfo also prefer people to use the latest
>> version.
>>
>> So why should emacs (of all projects) not use an up-to-date version of
>> makeinfo?  I don't see the problem at all.

Just today these new Texinfo directives caused trouble for me.
I successfully compiled CVS Emacs on quite an old GNU/Linux server
(Red Hat 9.0).  But there were only two errors in the whole build process:
in two Info files cc-mode.texi and rcirc.texi, since the version of Texinfo
on this server is 4.3:

makeinfo --force cc-mode.texi
cc-mode.texi:1628: Unknown command `headitem'.
cc-mode.texi:1661: Unknown command `headitem'.
make[1]: *** [../info/ccmode] Error 2

makeinfo --force rcirc.texi
rcirc.texi:122: Unknown command `indicateurl'.
rcirc.texi:122: Misplaced {.
rcirc.texi:122: Misplaced }.
rcirc.texi:428: Unknown command `indicateurl'.
rcirc.texi:428: Misplaced {.
rcirc.texi:428: Misplaced }.
make[1]: *** [../info/rcirc] Error 2

Due to these errors I was unable to consult the Info documentation from
the rest of Info files that should be created after the compilation that
was interrupted by makeinfo errors.  And I had no time/need to update
Texinfo on this server.

Please change back these two directives to backward-compatible ones.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  parent reply	other threads:[~2006-08-30 22:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 21:54 makeinfo 4.7 Kim F. Storm
2006-08-25 23:03 ` Eli Zaretskii
2006-08-25 23:35   ` Kim F. Storm
2006-08-26  8:11   ` Alan Mackenzie
2006-08-26 12:15     ` Eli Zaretskii
2006-08-26 12:46       ` Eli Zaretskii
2006-08-26 14:23         ` Alan Mackenzie
2006-09-01 17:55           ` Eli Zaretskii
2006-08-26 12:22 ` Richard Stallman
2006-08-26 17:11   ` Karl Berry
2006-08-27 14:34     ` Richard Stallman
2006-08-27 16:16       ` Eli Zaretskii
2006-08-27 16:26         ` David Kastrup
2006-08-27 22:27           ` Eli Zaretskii
2006-08-27 22:30             ` David Kastrup
2006-08-27 22:37               ` Eli Zaretskii
2006-08-27 23:03                 ` David Kastrup
2006-08-30  9:48                   ` Eli Zaretskii
2006-08-30  9:52                     ` David Kastrup
2006-08-28  8:20                 ` Kim F. Storm
2006-08-29 16:06                   ` Karl Berry
2006-08-29 16:49                   ` Stefan Monnier
2006-08-30 11:27                     ` Eli Zaretskii
2006-08-30 13:34                       ` Kim F. Storm
2006-08-30  9:57                   ` Eli Zaretskii
2006-08-30 11:20                     ` Kim F. Storm
2006-08-30 22:59                     ` Juri Linkov [this message]
2006-08-30 23:33                       ` David Kastrup
2006-08-31  2:42                         ` Miles Bader
2006-08-31  3:30                         ` Eli Zaretskii
2006-08-31 23:35                         ` Juri Linkov
2006-08-28 22:09         ` Richard Stallman
2006-08-30 10:44           ` Eli Zaretskii
2006-09-01 17:53             ` Eli Zaretskii
2006-08-28 15:14       ` Stefan Monnier
2006-08-30 10:32         ` Eli Zaretskii

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=87y7t5x4ur.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.org \
    --cc=storm@cua.dk \
    /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).