References in elisp.dvi.

References in elisp.dvi.

[Lute Kamstra]

For me, the page references in the Lisp Reference manual (elisp.dvi)
are incorrect.  Typically they are off by a few pages, but higher page
numbers are off more.  A few examples:

Page nr. mentioned     Actual page nr.
in reference.          of the section

  9                      9
 19                     19
 25                     25
 33                     32
 37                     35
 58                     56
 87                     85
150                    144
572                    566
735                    729
787                    781

Does anyone else see this?

  Lute.

Re: References in elisp.dvi.

[Alan Shutko]

Lute Kamstra <Lute.Kamstra@cwi.nl> writes:

> For me, the page references in the Lisp Reference manual (elisp.dvi)
> are incorrect.  Typically they are off by a few pages, but higher page
> numbers are off more.  A few examples:

Sounds like someone needs to do another TeX run to resolve the references.

-- 
Alan Shutko <ats@acm.org> - I am the rocks.
Easter kit on sale now! Comes with 2 boards, 3 nails and a martyr.

Re: References in elisp.dvi.

[Lute Kamstra]

Alan Shutko <ats@acm.org> writes:

> Lute Kamstra <Lute.Kamstra@cwi.nl> writes:
>
>> For me, the page references in the Lisp Reference manual (elisp.dvi)
>> are incorrect.  Typically they are off by a few pages, but higher page
>> numbers are off more.  A few examples:
>
> Sounds like someone needs to do another TeX run to resolve the references.

*Something* needs to run TeX another time.  I produce elisp.dvi by
doing "make elisp.dvi" in the lispref dir.  This should run TeX enough
times for the references to be calculated correctly (like texi2dvi
does), but it does not.  When I do another TeX run manually,
references are correct.

  Lute.

Re: References in elisp.dvi.

[Alan Shutko]

Lute Kamstra <Lute.Kamstra@cwi.nl> writes:

> *Something* needs to run TeX another time.  I produce elisp.dvi by
> doing "make elisp.dvi" in the lispref dir.

Oh, I didn't realize it was an automatic process.  (I thought you
were looking at a preproduced dvi, as has been announced here once in
a while, though not lately.)

I guess another tex run should be added to the makefile, or switch it
to texi2dvi.  It doesn't look like it's trying hard right now to get
the refs right.

-- 
Alan Shutko <ats@acm.org> - I am the rocks.
"You think I waited until I was sixteen to lose my virginity?"

Re: References in elisp.dvi.

[Eli Zaretskii]

> From: Lute Kamstra <Lute.Kamstra@cwi.nl>
> Date: Tue, 21 Oct 2003 19:03:15 +0200
> 
> *Something* needs to run TeX another time.  I produce elisp.dvi by
> doing "make elisp.dvi" in the lispref dir.  This should run TeX enough
> times for the references to be calculated correctly (like texi2dvi
> does), but it does not.  When I do another TeX run manually,
> references are correct.

Perhaps lispref/Makefile.in should be modified to use texi2dvi instead
of the good-ole way of running TeX ``by hand''.  texi2dvi repeatedly
runs TeX until the results actually stop changing, so it will always
produce the correct references.

Re: References in elisp.dvi.

[Andreas Schwab]

"Eli Zaretskii" <eliz@elta.co.il> writes:

>> From: Lute Kamstra <Lute.Kamstra@cwi.nl>
>> Date: Tue, 21 Oct 2003 19:03:15 +0200
>> 
>> *Something* needs to run TeX another time.  I produce elisp.dvi by
>> doing "make elisp.dvi" in the lispref dir.  This should run TeX enough
>> times for the references to be calculated correctly (like texi2dvi
>> does), but it does not.  When I do another TeX run manually,
>> references are correct.
>
> Perhaps lispref/Makefile.in should be modified to use texi2dvi instead
> of the good-ole way of running TeX ``by hand''.

lispref is a bit more complicated because it has this permute-index thing.
But maybe this can be dropped, it's not enabled by default anyway.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: References in elisp.dvi.

[Eli Zaretskii]

> From: Andreas Schwab <schwab@suse.de>
> Date: Tue, 21 Oct 2003 22:17:27 +0200
> 
> 
> lispref is a bit more complicated because it has this permute-index thing.
> But maybe this can be dropped, it's not enabled by default anyway.

It can be dropped, or we could run texi2dvi, then the permute-index
script and lastly, TeX.

In any case, I think the non-permuted_index branch of the elisp.dvi
target's commands should simply use texi2dvi.

Re: References in elisp.dvi.

[Richard Stallman]

    lispref is a bit more complicated because it has this permute-index thing.
    But maybe this can be dropped, it's not enabled by default anyway.

i would not mind.

Re: References in elisp.dvi.

[Andreas Schwab]

Richard Stallman <rms@gnu.org> writes:

>     lispref is a bit more complicated because it has this permute-index thing.
>     But maybe this can be dropped, it's not enabled by default anyway.
>
> i would not mind.

Ok, I've remove that now and switched to texi2dvi.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: References in elisp.dvi.

[Luc Teirlinck]

What is happenning with lispref/index.texi?  Each time I update, it
appears, but running `make bootstrap'  deletes it before it is neeeded,
causing bootstrapping to fail.   End of make bootstrap output:

ake[1]: Leaving directory `/home/teirllm/emacscvsdir/emacs/leim'
(cd man; make  info)
make[1]: Entering directory `/home/teirllm/emacscvsdir/emacs/man'
make[1]: Nothing to be done for `info'.
make[1]: Leaving directory `/home/teirllm/emacscvsdir/emacs/man'
(cd lispref; make  info)
make[1]: Entering directory `/home/teirllm/emacscvsdir/emacs/lispref'
make[1]: *** No rule to make target
`/home/teirllm/emacscvsdir/emacs/lispref/index.texi', needed by
`/home/teirllm/emacscvsdir/emacs/lispref/../info/elisp'.  Stop.
make[1]: Leaving directory `/home/teirllm/emacscvsdir/emacs/lispref'
make: *** [info] Error 2

index.texi is indeed gone.

lispref/Makefile.in contains:

clean:
rm -f *.toc *.aux *.log *.cp *.cps *.fn *.fns *.tp *.tps*.vr *.vrs *.pg *.pgs *.ky *.kys
rm -f make.out core
rm -f index.texi

Why that last line?  Should `make clean' really remove index.texi?
Even if so, certainly `make bootstrap' should not.

Sincerely,

Luc.

Re: References in elisp.dvi.

[Andreas Schwab]

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> Why that last line?  Should `make clean' really remove index.texi?

No, it should not.  I'll fix that in a minute.  Workaround is to build in
a separate directory.

Sorry for the breakage.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: References in elisp.dvi.

[Richard Stallman]

    > Why that last line?  Should `make clean' really remove index.texi?

    No, it should not.  I'll fix that in a minute.  Workaround is to build in
    a separate directory.

if the makefile creates index.texi, and it's not in the distro,
make clean shd delete it.

if index.texi is now precreated and in the tar ball,
then make ckean shd not delete it.

in make bootstrap, the second make shd create it again.
that's the way to avoid this error.

Re: References in elisp.dvi.

[Stefan Monnier]

> in make bootstrap, the second make shd create it again.
> that's the way to avoid this error.

BTW, why does bootstrap do all those `clean' steps?  The few times I call
`bootstrap' I find those steps just waste my time by removing and rebuilding
files in the exact same way.  I'd rather call the bootstrap-clean-before
step manually when needed.  It's especially annoying when the bootstrap
fails partway because "fix && make boostrap" will start all over from
scratch each and every time.


        Stefan

Re: References in elisp.dvi.

[Luc Teirlinck]

While on the subject of lispref/Makefile.in:

maintainer-clean: clean
		  rm -f elisp elisp-* elisp.dvi elisp.oaux

Is elisp.oaux really what is meant or should that be elisp.aux?

Sincerely,

Luc.

Re: References in elisp.dvi.

[Luc Teirlinck]

>From my previous message:

   Is elisp.oaux really what is meant

Apparently yes, since it is mentioned in the Change Log.  Sorry for
the false alarm on this one.

Sincerely,

Luc.

Re: References in elisp.dvi.

[Andreas Schwab]

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> While on the subject of lispref/Makefile.in:
>
> maintainer-clean: clean
> 		  rm -f elisp elisp-* elisp.dvi elisp.oaux
>
> Is elisp.oaux really what is meant or should that be elisp.aux?

No, *.aux is already cleaned up.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: References in elisp.dvi.

[Richard Stallman]

    Perhaps lispref/Makefile.in should be modified to use texi2dvi instead
    of the good-ole way of running TeX ``by hand''.  texi2dvi repeatedly
    runs TeX until the results actually stop changing, so it will always
    produce the correct references.

sounds good to me.