On Mon, Aug 20, 2012 at 10:43:54AM +0100, Phil Holmes wrote: > "eluze" <[email protected]> wrote in message > news:[email protected]... > >running the command > > > >lilypond -dseparate-log-files a.ly ab.ly > > > >results in: > > > >GNU LilyPond 2.15.95 > >C:/Program Files > >(x86)/LilyPond/usr/share/lilypond/current/scm/lily.scm:807:15: In > >procedure > >open-file in expression (open-file (if # # ...) "a"): > >C:/Program Files > >(x86)/LilyPond/usr/share/lilypond/current/scm/lily.scm:807:15: No > >such file > >or directory: "/dev/stderr" > > > >workaround (for windows): > > > >FOR %x IN (*.ly) DO lilypond %x [1>"%~nx.out"] 2>"%~nx.log" > > > >did I use this command/option incorrectly? if not I will add this to the > >issue list. > > Definite bug for windows. Don't believe dev/stderr should be used here: > > (open-file (if (string-or-symbol? (ly:get-option 'log-file)) > (format #f "~a.log" (ly:get-option 'log-file)) > "/dev/stderr") "a") #f)) > > > David will know, but I suspect current-error-port or somesuch should > be used.
Looks like there are two bugs here: 1. Eluze reported that -dseparate-log-files does not work on Windows. 2. Lilypond running on Windows attempted to use /dev/stderr, which is not available on the Windows platform. I see that David has opened a tracker for the code attempting to use /dev/stderr. http://code.google.com/p/lilypond/issues/detail?id=2759 I'll create a tracker for the -dseparate-log-files problem. Cheers, Colin. -- Colin Hall _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
