Re: Call for testers: prerelease Xemacs auctex-1.44 (sync with11.54)

David Kastrup <[email protected]>
Newsgroups gmane.emacs.auc-tex
Message-ID <[email protected]>
Uwe Brauer <[email protected]> writes:

>>>>>> "David" == David Kastrup <[email protected]> writes:
>
>     David> Uwe Brauer <[email protected]> writes:
>     >> I just successfully committed the patch with synch the xemacs auctex
>     >> pkg with 11.54.
>     >> 
>     >> I would like to ask the users to test this new release, especially
>     >> users which use Miktex in the MS windows environment.
>     >> 
>     >> An important point is to know whether the variable 
>     >> TeX-macro-global has been set correctly.
>
>     David> It still erroneously claims in tex.elc
>
>     David> (defconst AUCTeX-version "CVS-1.11")
>     David> (defconst AUCTeX-date "2005.0118")
>
> I am aware of this problem.

>     David> We already had   this  the last release.   Please,   before
>     David> checking stuff into CVS  for XEmacs, replace the AUCTeX CVS
>     David>  strings manually with  the  correct version numbers.  This
>     David> needs to be done in tex.el.
>
> We had this discussion as far as I can recall the problem is caused
> by using CVS, that is I change the version number and I commit it
> CVS change the number. If you tell me how to change the version
> number without using CVS I do it.

It is still like the last time we discussed this.  You just write
(defconst AUCTeX-version "11.54")
(defconst AUCTeX-date ...

instead of the respective lines in tex.el.  You have to take the
version numbers out of the control of CVS strings like $Release: $ if
you are going to use CVS and/or RCS on the file.

Alternatively, you have to tell your CVS system that tex.el is to be
considered a binary file, and so no keyword replacements are to be
done at all.

You can do that with cvs.

(info "(cvs) Binary howto")

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.