Werner LEMBERG <[email protected]> writes:
>>> 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.
>>
>> Exactly the behaviour that I want.
>
> Certainly not.
>
>> When I work on manuscripts the .pdf (as well as the .midi) are
>> objects. The .ly is the only source. Just like compiling .c files,
>> I don't want a warning every time it is going to overwrite a .o
>> file.
>
> There is a big difference: If you compile a .c file, the .o files
> stays by default; the compiler doesn't remove it.
Uh, wrong?
cd /tmp;echo "main(){return 0;}" >gega.c;gcc -o gega gega.c;ls gega*
gega gega.c
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
