Hello,
On 09/08/18 19:02, Aaron Hill wrote:
On 2018-08-09 08:41, James Lowe wrote:
Sorry this took so long for me to get back to you.
More research tells me that it is not lilypond that is at fault here
but Windows.
Windows cmd does not support UNC paths.
That should not be relevant, thoug
Knute,
On 09/08/18 18:30, Karlin High wrote:
On 8/9/2018 10:41 AM, James Lowe wrote:
Windows cmd does not support UNC paths.
Does it work if the UNC path gets mapped as a network drive? That
could even be automated on the command line with the NET USE command.
That is effectively, as far
On 2018-08-09 08:41, James Lowe wrote:
Sorry this took so long for me to get back to you.
More research tells me that it is not lilypond that is at fault here
but Windows.
Windows cmd does not support UNC paths.
That should not be relevant, though. That at most limits the ability
for the cu
On 8/9/2018 10:41 AM, James Lowe wrote:
Windows cmd does not support UNC paths.
Does it work if the UNC path gets mapped as a network drive? That could
even be automated on the command line with the NET USE command.
--
Karlin High
Missouri, USA
___
Hello Knute,
On 24/04/18 16:50, Knute Snortum wrote:
> My tests on Windows 10 indicate that lilypond.exe can't handle UNC
> notation. This is true even of a local file.
>
> First I "type" the file and it works fine with UNC. Then I try
to launch
> LilyPond with the sa
