From: "Eli Zaretskii" <eliz@gnu.org>
Cc: storm@cua.dk, belanger@truman.edu, Lute.Kamstra.lists@xs4all.nl,
emacs-devel@gnu.org
Subject: Re: texinfo.tex change.
Date: Thu, 10 Feb 2005 06:47:59 +0200 [thread overview]
Message-ID: <01c50f2b$Blat.v2.4$d768b0e0@zahav.net.il> (raw)
In-Reply-To: <87hdklaxh2.fsf@vh213602.truman.edu> (message from Jay Belanger on Wed, 09 Feb 2005 21:46:17 -0600)
> From: Jay Belanger <belanger@truman.edu>
> Date: Wed, 09 Feb 2005 21:46:17 -0600
> Cc: emacs-devel@gnu.org, belanger@truman.edu, "Kim F. Storm" <storm@cua.dk>
>
> >> makeinfo --version says:
> >>
> >> makeinfo (GNU texinfo) 4.3
>
> I currently have Texinfo 4.8.
> I'll add a definition for @LaTeX in calc.texi, so it won't matter
> which version of makeinfo is used (I hope).
Please don't: you cannot do that in a way that would avoid problems
with versions of Texinfo that do support @LaTeX.
> > @LaTeX{} was introduced in Texinfo 4.7 (9 April 2004). I'll update
> > README that currently says that Texinfo 4.2 or later is needed.
>
> The change to calc.texi will still be needed.
Why do we need to use @LaTeX{} in calc.texi? What's so important
about this macro that it must be used there?
In general, we don't want to force users to install too recent
versions of Texinfo, so the very recent introductions should be
avoided if possible.
next prev parent reply other threads:[~2005-02-10 4:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <876513nswn.fsf@xs4all.nl>
2005-02-08 12:59 ` texinfo.tex change Kim F. Storm
2005-02-08 13:26 ` Lute Kamstra
2005-02-08 13:44 ` Lute Kamstra
2005-02-08 14:16 ` Jay Belanger
2005-02-09 23:03 ` Kim F. Storm
2005-02-09 23:47 ` Lute Kamstra
2005-02-10 3:46 ` Jay Belanger
2005-02-10 4:47 ` Eli Zaretskii [this message]
2005-02-10 5:28 ` Jay Belanger
2005-02-11 14:45 ` Eli Zaretskii
2005-02-10 13:43 ` Robert J. Chassell
2005-02-10 19:19 ` Jay Belanger
2005-02-10 18:40 ` Richard Stallman
2005-02-10 18:57 ` Jay Belanger
2005-02-10 19:11 ` David Kastrup
2005-02-12 8:37 ` Richard Stallman
2005-02-12 16:26 ` Jay Belanger
2005-02-13 16:11 ` Stefan Monnier
2005-02-10 6:01 ` Richard Stallman
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='01c50f2b$Blat.v2.4$d768b0e0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=Lute.Kamstra.lists@xs4all.nl \
--cc=belanger@truman.edu \
--cc=emacs-devel@gnu.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).