Re: [bug #43122] texi2dvi does not compile enough times to get toc

[Vincent Belaïche]

Answers below...

Le 09/09/2015 02:14, Gavin Smith a écrit :

[...]

>
> Vincent mentioned the problem of the efficiency of running the test
> for --recorder every time. I don't think it's a problem: if it led to
> a noticeable slowdown (maybe tenth of a second or so) that would be a
> problem. There could be other ways to improve efficiency though. I
> don't like the idea of adding lots of knobs to tweak performance and
> internal implementation, when it should be good by default.
>

Well, I agree with you that tweaking just for performance when it is not
worth it is just another source of problem. However :

1) I think that it is worth it, that openout test is noticeable
   processing-time-wise : there is a file created and a tex run. Anyway,
   you can also argue that when one really needs performance because
   he/she writes a document and wants WYSIWYGing it, he/she won't run
   texi2dvi but rather run manually individual tools.

2) I think that it is anyway needed for debug and testing, whichn, yes,
   the plain user does not need to know, until, as Karl suggested,
   he/she meets another bug.

> Once again, I'd be happy enough to put it in the manual if others see
> a need for it.

That is fine to me to do that, provided that there is some "see manual
info node texi2dvi gory details for expert options/envars" in the help
message, and we create that info node about the gory details. In the
nodes about envvar & options we just put a link to this node also for
the TEXI2DVI_USER_RECORDER envvar and -u / --use-recorder option.

I think that this way we would make the information available to the
user, but at the same time the manual and help message reading would be
smoother as the bulk of it is in a separate "gory details" node.

  V.


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
http://www.avast.com