Be smarter with engine reruns

reitzig / ltx2any

Yet another LaTeX build wrapper, with one or two nifty features

GNU General Public License v3.0

59 stars 4 forks source link

Be smarter with engine reruns #67

Open akerbos opened 8 years ago

akerbos commented 8 years ago

We can use hashes to do two things:

In daemon mode, carry over hashes between runs. If the hash after engine run nr 1 is the same as as before, no rerun is needed (except if extensions run).

Is this even possible between independent runs without -c?
If a fixed number of iterations is given by -n, warn the user
- that the result may not have been final (if hashes have not converged) or
- that some runs where unnecessary (of hashes not change).

akerbos commented 8 years ago

Attack together with #58.

After refactoring of hashing business, the way is paved for this one.

akerbos commented 8 years ago

Note to self: pimp HashManager.files_changed? to deal with without and drop_from parameters? Can that help with being smarter in the above sense?

koppor commented 8 years ago

Does the package logreq help here? As far as I understood, one can just prepend \RequirePackage{logreq} before \documentclass. Maybe this can be done somehow automatically. I remember that TeX4ht does something like that when translating.

Side comment: Your approach seems the one of rerunfilecheck, isn't it?

akerbos commented 8 years ago

@koppor Thanks for these pointers!

logreq does not seem in a position where you can rely on it providing all the information. In general, relying on document and/or package authors to do something is contrary to my design goals here.
rerunfilecheck does indeed seem to do something similar. It is more targetted since it requires (package) authors to specify which files to check, but is therefore almost certainly incomplete.

From my perspective, there is no general way to solve the "rerun problem" but from the outside, if there is one at all.

koppor commented 2 years ago

Maybe focussing on one (maintained) solution could make the result a) reusable across multiple tools and b) having a (larger) community maintaining the rules (refs https://github.com/ho-tex/rerunfilecheck/issues/1)... - Maybe I see too much help in the synergy for too little cases.