Re: texi2dvi changes

2017-06-21 Thread Gavin Smith
On Wed, Jun 21, 2017 at 08:28:12PM +0100, Gavin Smith wrote: > On Fri, Sep 25, 2015 at 09:42:51AM +0100, Gavin Smith wrote: > > Now only the files that are directly produced are compared, not the > > sorted index files. > > This has the unfortunate effect that if the sorted index files are >

Re: texi2dvi changes

2017-06-21 Thread Gavin Smith
(replying to old message) On Fri, Sep 25, 2015 at 09:42:51AM +0100, Gavin Smith wrote: > Now only the files that are directly produced are compared, not the > sorted index files. This has the unfortunate effect that if the sorted index files are missing but the unsorted index files aren't,

Re: texi2dvi changes

2015-09-25 Thread Vincent Belaïche
[...] > > They you can't know what the next step if (bibtex, makeglossaries, > biber, makeindex, texindex, ...)... > [...] I meant "The*n* you can't know what the next step i*s*" Sorry for the typoes, Vincent. --- L'absence de virus dans ce courrier électronique a été vérifiée par le

Re: texi2dvi changes

2015-09-25 Thread Gavin Smith
On 24 September 2015 at 21:54, Vincent Belaïche wrote: >> I pointed out that the log files were being grep'd a lot to get the >> list of generated files. This won't happen as much now. >> > > I have seen that what you have done goes far beyond reverting the > TEXINPUTS

Re: texi2dvi changes

2015-09-25 Thread Vincent Belaïche
Le 25/09/2015 10:42, Gavin Smith a écrit : > On 24 September 2015 at 21:54, Vincent Belaïche > wrote: >>> I pointed out that the log files were being grep'd a lot to get the >>> list of generated files. This won't happen as much now. >>> >> [...] > > IIRC this

Re: texi2dvi changes

2015-09-23 Thread Gavin Smith
On 22 September 2015 at 23:34, Karl Berry wrote: > gs> Can anybody try the script with LaTeX source with BibTeX, or > else send me a test case? I want to make sure the BibTeX files are > checked properly. > > > % bibsimple.tex >

Re: texi2dvi changes

2015-09-23 Thread Karl Berry
+ if test $generated_files_get_method = generated_files_get_from_fls; then +if test -f "$in_noext.fl"; then + report 'WARNING!! You may typeset garbage!' # goes to stderr +fi + fi (Aside: I usually find test -r more useful than test -f, because if by some weird

Re: texi2dvi changes

2015-09-22 Thread Gavin Smith
On 22 September 2015 at 23:55, Karl Berry wrote: > Hi Gavin, > > gs> If someone uses an "fl" index with the recorder, I expect either > the index to be blank, or to be the recorder file interpreted as TeX > source (a great ugly mess). > > There's a comment in

Re: texi2dvi changes

2015-09-22 Thread Karl Berry
Hi Gavin, gs> If someone uses an "fl" index with the recorder, I expect either the index to be blank, or to be the recorder file interpreted as TeX source (a great ugly mess). There's a comment in texi2dvi that says # The default behaviour is `nomaybe'. But the actual default for

Re: texi2dvi changes

2015-09-22 Thread Gavin Smith
On 22 September 2015 at 23:55, Karl Berry wrote: > Excuse my opinion, but this seems like the worst possible outcome. This > way, an existing document that uses an fl index (as discussed, they > exist) will silently typeset garbage with a new texi2dvi. Thus, with > the

Re: texi2dvi changes

2015-09-22 Thread Karl Berry
gs> Can anybody try the script with LaTeX source with BibTeX, or else send me a test case? I want to make sure the BibTeX files are checked properly. % bibsimple.tex \documentclass{article} \begin{document} \nocite{*} \bibliographystyle{plain} \bibliography{xampl}

Re: texi2dvi changes the behavior of ~

2009-05-04 Thread Karl Berry
Hi Akim, How is this code expected to disable the magic tricks it plays with ~? It should only be enabled when the source is texinfo, not latex. Can you make that change? The way things have turned out, I rather think latex2dvi should have been a separate script. Most of what's in texi2dvi