----- Original Message -----
From: "David Kastrup" <[email protected]>
To: "Phil Holmes" <[email protected]>
Cc: "Phil Burfitt" <[email protected]>; <[email protected]>
Sent: Thursday, October 17, 2013 3:06 PM
Subject: Re: Frescobaldi 2.0.11
"Phil Holmes" <[email protected]> writes:
----- Original Message -----
From: "David Kastrup" <[email protected]>
To: "Phil Burfitt" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, October 17, 2013 2:47 PM
Subject: Re: Frescobaldi 2.0.11
"Phil Burfitt" <[email protected]> writes:
Hi David,
lilypond -l DEBUG -I "c:/trial" test.ly 2> output.txt
Any difference if you get upper/lowercase of "c:/trial" exactly
corresponding to what DIR C:\ shows?
--
David Kastrup
I doubt whether that would cause a problem on a Windows system -
filenames and directories are case-insensitive. I'm thinking c:\trial
instead of c:/trial should be tried - this is the windows directory
separator.
But the other paths, including paths where .ly files _are_ being found
(like with \include "declarations-init.ly") are displayed with / as well
but with C: in them.
So what's different with them?
--
David Kastrup
The directory "trial" is lowercase.
However I've tried with...
c:\trial
c:/trial
C:\trial
C:/trial
C:\TRIAL
C:/TRIAL
all treated the same and same output. Under Windows/DOS you can use "\" or
"/" for paths and changing directories etc.
fwiw, if I use \include "c:\trial\functions.ly" lilypond compiles fine but
warns about normalizing filenames...prefers \include "c:/trial/functions.ly
Phil.
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
