On 2024-09-16 07:19, Knute Snortum wrote:
On Sun, Sep 15, 2024 at 10:46 PM Stu McKenzie via LilyPond User List
wrote:
I use \bookOutputName to generate different output files, but when
I try a full output path, or a folder path, in LilyPond, they are
ignored.
My previous "a
On Sun, Sep 15, 2024 at 10:46 PM Stu McKenzie via LilyPond User List <
swwlilyu...@stoozsoftware.com> wrote:
>
> I use \bookOutputName to generate different output files, but when I try a
> full output path, or a folder path, in LilyPond, they are ignored.
> My previous "acceptable" options within
Reply to Saul Tobin at the end...
On 2024-09-15 16:21, Saul Tobin wrote:
You might find it more convenient to define the output PDF filename
directly within Lilypond. See:
https://lilypond.org/doc/v2.24/Documentation/notation/output-file-names
or for 2.25
https://lilypond.org/doc/v2.25/Docum
You might find it more convenient to define the output PDF filename
directly within Lilypond. See:
https://lilypond.org/doc/v2.24/Documentation/notation/output-file-names or
for 2.25
https://lilypond.org/doc/v2.25/Documentation/notation/output-file-names.
On Sun, Sep 15, 2024 at 5:18 PM Stu McKenz
Reply to Knute Snortum at the end...
On 2024-09-15 12:48, Knute Snortum wrote:
On Sun, Sep 15, 2024 at 11:59 AM Stu McKenzie via LilyPond User List
wrote:
I've encountered an issue whereby I can make a PDF output to a
different
file or folder using Command Prompt on Windows, e
On Sun, Sep 15, 2024 at 11:59 AM Stu McKenzie via LilyPond User List <
swwlilyu...@stoozsoftware.com> wrote:
>
> I've encountered an issue whereby I can make a PDF output to a different
> file or folder using Command Prompt on Windows, e.g.:
>
> "C:/Program Files (x86)/LilyPond2p24p0/lilypond-2.24
