Issue 635 in lilypond: LilyPond deletes PDF instead of just writing new contents in the file

[codesite-noreply]

Issue 635: LilyPond deletes PDF instead of just writing new contents in 
the file
http://code.google.com/p/lilypond/issues/detail?id=635

New issue report by wbsoft:
In scm/backend-library at line 114-115, the output PDF file is first
deleted before a new one is written:

   (if (access? pdf-name W_OK)
       (delete-file pdf-name))

But this breaks the PDF watching feature of KDE, because KDE looses the
watch on the file because it is deleted. When the file is recreated, it
has a different inode number, and other attributes on the former PDF are
lost as well.

Commenting or deleting the two lines does not seem to do any harm on my
system, and it fixes greatly the behaviour of KPDF and Okular. And file
access rights and other properties are kept as well.

Attached patch removes these lines from backend-library.scm.



Attachments:
        nodelete-pdf.patch  426 bytes


Issue attributes:
        Status: New
        Owner: ----
        Labels: Type-Defect Priority-Medium

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