On Fri, 1 May 2015, Martin Tarenskeen wrote:
The bug would be fixed if lilypond would make ghostscript use a complete path
to the intermediate lines.ps file for the ps to pdf conversion.
The issue has brought me to another problem:
LilyPond by default takes *.ly file as input and produces a *.pdf file as
output.
$lilypond example.ly ---> result: example.pdf
In this case, as an intermediate file "example.ps" is used. This is a
problem if a file named "example.ps" already exists in my working
directory. This file is brutally overwritten and deleted when I run
lilypond without any warning or option to cancel, nor is a backup copy of
the old file made.
If the intermediate file would be given a unique, not already existing,
temporary filename, not only this issue would be solved but also the
original "lines.ly -> lines.ps -> lines.pdf" issue that started this
thread would not be a problem anymore.
I'm not a (LilyPond) developer but does it makes sense what I am
suggesting?
--
MT
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
