Issue 635 in lilypond: PDF automatic deletion is unconvenient on GNU/Linux

[codesite-noreply]

Comment #17 on issue 635 by flamingspinach: PDF automatic deletion is  
unconvenient on GNU/Linux
http://code.google.com/p/lilypond/issues/detail?id=635

If you can't write to a file, you usually can't delete it either, right? I  
was
thinking more along the lines of having LilyPond itself fail with "couldn't  
write to
output pdf". LilyPond currently fails anyway when it can't delete the file,  
so as far
as I can tell it wouldn't make LilyPond fail in any additional situations  
if my
suggestion were to be implemented, and would only eliminate some situations  
in which
it does fail but has no need to.

--
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