Masamichi Hosoda wrote > ... > However, I think that the "intermediate" file should be temporary > by mkstemp etc. > If lilypond uses mkstemp generated temporary file, > this ghostscript problem will not occur. > > _______________________________________________ > lilypond-user mailing list
> lilypond-user@ > https://lists.gnu.org/mailman/listinfo/lilypond-user Well, I often explicitly want both files to be created during one compilation: 1. the 'page by page' PDF, with point-and-click-links (usually A4 sheet size) 2. the PS file, because it's used for another postprocessing: I generate a booklet layout PDF from it (this PDF uses the double sheet size, e.g. A3) Therfore, if someone explicitly want's the keep the intermediate PS file, it shall not be using a temporary file name. Moreover, often I generate a third PDF, too - one just like the first PDF, but the textedit links removed. I implemented this by a patch to scm/backend-library.scm [LSR 992, not approved jet]. I could look how to convert the file name from relative to absolute path there in the procedure postscript->pdf, but the same has to be done for all other final conversion which use an intermediate postcript file, too. ArnoldTheresius -- View this message in context: http://lilypond.1069038.n5.nabble.com/my-favorite-bug-tp175778p176024.html Sent from the User mailing list archive at Nabble.com. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user