Remember to CC the mailing list or reply all!
On Thu, Feb 13, 2025, 8:40 AM SK <s.skr.k...@googlemail.com> wrote:
> Hello, thank you for your answer. I will post the output using debug as
> soon as I'm back on the computer. However, I noticed the following
> yesterday: If I change the output directory of my command to, say,
> "D:\test", it runs and generates the .tex files. "test" didn't exist
> before. But, deleting my original output directory and running the command
> again fails with the same error. I would suspect some problems with the
> long path, but I know it worked before without actually changing anything
> on lilypond.
> Kind regards!
>
> Am Do., 13. Feb. 2025 um 00:33 Uhr schrieb Knute Snortum <
> ksnor...@gmail.com>:
>
>> On Wed, Feb 12, 2025 at 8:53 AM SK <s.skr.k...@googlemail.com> wrote:
>>
>>> Hello,
>>>
>>> since a few days I cannot use a script involving lilypond-book anymore.
>>> It's really strange cause I don't remember to change anything for the
>>> script, the included python or lilypond itself. Only thing I did was
>>> cleaning up the output directory by deleting old files - as far as I
>>> understand this should not change the behaviour of the script.
>>> I'm on Windows 10, lilypond 2.24.4
>>>
>>> Here is the error:
>>> C:/Users/xxx/Documents/lilypond/share/lilypond/2.24.4/ly/init.ly:65:2:
>>> error: Guile signaled an error for the expression beginning here
>>> #
>>> (let ((book-handler (if (defined? 'default-toplevel-book-handler)
>>> Throw to key `system-error' with args `(("open-fdes" "~A" ("No such file
>>> or directory") (2)))'.
>>> Command 'lilypond --formats=ps -I
>>> "D:\xxx\Dropbox\Dropbox\Songbook\Sample" -daux-files -dinclude-eps-fonts
>>> -dgs-load-fonts -dseparate-page-formats=eps,pdf --loglevel=ERROR
>>> -dread-file-list -dno-strip-output-dir
>>> "C:/Users/xxx/Desktop/Tools/Songbook/Sample/pyOut/
>>> snippet-names-387c018110e42acaf491e2ef65eae35c.ly"' returned non-zero
>>> exit status 1.
>>>
>>> Any help would be very much appreciated, I could find nothing online to
>>> solve this issue.
>>>
>>> Kind regards!
>>>
>>
>> Is it possible that a file needed by the LilyPond source file was one of
>> those deleted? What about setting the log level to DEBUG and see if that
>> gives you any more clues?
>>
>> --
>> Knute Snortum
>>
>>
