[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Li
From: |
codesite-noreply |
Subject: |
Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux |
Date: |
Wed, 22 Jul 2009 18:15:00 +0000 |
Comment #16 on issue 635 by wbsoft: PDF automatic deletion is unconvenient
on GNU/Linux
http://code.google.com/p/lilypond/issues/detail?id=635
That would be a nice idea. I don't know how to code that unfortunately. The
file
would not need to be deleted in scm/backend-library.scm, but GhostScript is
the one
that's going to write to the output PDF. So LilyPond should then just call
gs and is
that fails with some 'cant write to output pdf' error, delete the PDF file
and then
try again. But that's hairy too, because there could be other reasons for
failing to
write to a file, besides it being opened by another application...
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux, codesite-noreply, 2009/07/21
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux, codesite-noreply, 2009/07/22
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux, codesite-noreply, 2009/07/22
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux, codesite-noreply, 2009/07/22
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux, codesite-noreply, 2009/07/22
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux,
codesite-noreply <=
- Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux, codesite-noreply, 2009/07/22