Re: my favorite bug :-)

[Werner LEMBERG]

>> 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.  However, lilypond,
if called with option `--pdf' (which is the default), *does* remove
the intermediate .ps file!

>> If the intermediate file would be given a unique, not already
>> existing, temporary filename, not only this issue would be solved but
> 
> Solved for some, problem for others.  I don't want to have to guess
> what my final manuscript is named.  If I start with example.ly I
> know that example.pdf is my target.  Scripts can deal with that
> easily.

Perhaps a misunderstanding: If I say

  lilypond --pdf foo.ly

I get `foo.pdf', no question.  If I say

  lilypond --os foo.ly

I get `foo.ps'.  However, the former call creates an intermediate file
`foo.ps' that gets deleted eventually by lilypond itself.  And this is
bad.

>> also the original "lines.ly -> lines.ps -> lines.pdf" issue that
>> started this thread would not be a problem anymore.
> 
> Different issue.

No, not at all.


    Werner