When a compilation of a TeX file fails, the user doesn't get any feedback on what the problem was. In the current version of FysikRevyTeX, a compilation failure will trigger a prompt asking the user whether the compilation should be done again, this time with output.
Compiling again is a waste of time, and (what is worse) this approach doesn't even work when compiling in parallel (which we want!). In fact, a compilation failure when compiling in parallel can be very hard to identify, as the real problem is hidden behind lots of multiprocessing output.
Possible solutions:
Let the compilation of other files continue, and at the end show a list of failed files. Do not remove .log files for these files.
Maybe present the .log files using e.g. less and when the user exits, the program will ask if it should try recompiling the file, assuming the user has fixed the problems.
When a compilation of a TeX file fails, the user doesn't get any feedback on what the problem was. In the current version of FysikRevyTeX, a compilation failure will trigger a prompt asking the user whether the compilation should be done again, this time with output.
Compiling again is a waste of time, and (what is worse) this approach doesn't even work when compiling in parallel (which we want!). In fact, a compilation failure when compiling in parallel can be very hard to identify, as the real problem is hidden behind lots of
multiprocessingoutput.Possible solutions:
lessand when the user exits, the program will ask if it should try recompiling the file, assuming the user has fixed the problems.