[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Lilypond does not set the output filename, but rather a basename (withou
From: |
Sebastiano Vigna |
Subject: |
Lilypond does not set the output filename, but rather a basename (without prefix) |
Date: |
Thu, 27 Jan 2005 12:19:44 +0100 |
The documentation for Lilypond says that
-o, --output=FILE
write output to FILE
But this is not true:
lilypond --tex -obug.foo bug.ly
GNU LilyPond 2.4.3
Processing `bug.ly'
Parsing...
Interpreting music... [2]
Preprocessing graphical objects...
Calculating line breaks... [2]
Layout output to `bug.foo.tex'...
That is, depending on the output, some suffix appears to be always
added. This happens even if the correct suffix is already there:
lilypond --tex -obug.tex bug.ly
GNU LilyPond 2.4.3
Processing `bug.ly'
Parsing...
Interpreting music... [2]
Preprocessing graphical objects...
Calculating line breaks... [2]
Layout output to `bug.tex.tex'...
Probably changing the behaviour to match exactly the documentation is
not feasible, but it would be nice that Lilypond did not add extensions
to the specified file if it already has one.
Even better, of course, would be a behaviour matching the docs.
--
Ciao,
seba
- Lilypond does not set the output filename, but rather a basename (without prefix),
Sebastiano Vigna <=