Re: RefTeX Merge

[Ralf Angeli <angeli@caeruleus.net>]

* Glenn Morris (2012-09-23) writes:

> Ralf Angeli wrote:
>
>> * Version info in Lisp and Texinfo files
>
> This is not really an option for Emacs, because the info and elc files
> are pre-built in release tarfiles. So people don't even need to have
> makeinfo installed to build Emacs. So you cannot generate parts of the
> *.texi files at build time. This is why eg doc/emacs/emacsver.texi is
> not generated by configure.

Ah, okay.  But emacsver.texi is sort of what I was looking for.  Even
though it is not automatically generated, the version information in
there could be used in reftex.texi.  (As long as people are content with
RefTeX using the same version as Emacs.)

emacsver.texi lacks information about the date which can be used to
distinguish different builds during the development phase.  And I found
it nice to see how old a (released) version is.  But I guess it's not
too much of a loss if that bit of information is removed from the
manual.

>> * Macros in Texinfo files
>
> It depends which version of makeinfo they first appeared in. @TeX and
> @LaTeX are used already elsewhere in Emacs, so are OK. I've never heard
> of @BibTeX, and it is not in the texinfo 4.13 manual on my current
> machine. Configure currently tests for makeinfo >= 4.7.

As you suspected in another mail I was talking about user-defined macros
where I was not sure if they can be used.  Since they don't seem to be
problematic I'll leave them in reftex.texi.

In the standalone version there is a macro.texi file which is included
in reftex.texi but for the Emacs version I've put everything in
reftex.texi.  The same is true for install.texi with installation
instructions (which should be removed at some point in time) and
changes.texi with news related to releases.

-- 
Ralf