On Thu, Apr 29, 2010 at 8:32 PM, Carl Sorensen wrote:
> On 4/27/10 10:49 PM, "Nathan Reed" wrote:
>
>> Lilypond would attempt to delete the output PDF before overwriting it in
>> Windows
>> (but no other platforms). This is unnecessary and causes problems with
>> certain
>> PDF viewers, e.g. Sum
On 4/27/10 10:49 PM, "Nathan Reed" wrote:
> Lilypond would attempt to delete the output PDF before overwriting it in
> Windows
> (but no other platforms). This is unnecessary and causes problems with
> certain
> PDF viewers, e.g. Sumatra, where the PDF is kept open in a way that allows
> overwri
On Wed, Apr 28, 2010 at 2:48 PM, Carl Sorensen wrote:
> Have you tested your patch with other PDF viewers to verify that the
> behavior is not worse with them?
I've tested with Foxit Reader and Adobe Reader. The behavior with Foxit is
improved; Lilypond can overwrite the PDF, though Foxit does
On 4/27/10 10:49 PM, "Nathan Reed" wrote:
> Lilypond would attempt to delete the output PDF before overwriting it in
> Windows
> (but no other platforms). This is unnecessary and causes problems with
> certain
> PDF viewers, e.g. Sumatra, where the PDF is kept open in a way that allows
> over
Lilypond would attempt to delete the output PDF before overwriting it in Windows
(but no other platforms). This is unnecessary and causes problems with certain
PDF viewers, e.g. Sumatra, where the PDF is kept open in a way that allows
overwriting but not deletion. See also the discussion on bug-l
