Closed jperon closed 5 years ago
A drawback of this is that, in case of LilyPond failures, there will be misleading messages about unrecognized commands. IMHO, it isn't such an issue.
Just pushed changes: there's now a function to detect whether we are on MiKTeX, and to adjust cmd accordingly. Nevertheless, I kept the re-run with debug (locally) activated, to avoid useless recompiles.
@uliska When it's merged, I think we could release 1.0 final.
@jperon sorry I didn't process anything the last days.
For a final release we should go through the manual once more to check if anything was missed or to find any remaining flaws. -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
@uliska Do you think you could do that ? I must confess that doc isn't my cup of tea…
I'll have a look and see what happens... -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Fix #204: MiKTeX behavior isn't the same as TexLive's with io.popen. I don't know why, but on MiKTeX, we have to add a level of quotes, and it doesn't seem to be able to write code to stdin.
Incidentally, when LilyPond fails on a score, compilation is re-tried with debug=true.