Re: \include command and local network folders

On Tue 24 Apr 2018 at 00:42:32 (-0700), foxfanfare wrote: > 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. > > Let me wonder if everybody here use linux! > Maybe is it time for me to go for it... All the

Re: \include command and local network folders

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. Let me wonder if everybody here use linux! Maybe is it time for me to go for it... -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Re: \include command and local network folders

On Sun, Apr 22, 2018 at 5:48 PM, David Wright wrote: > On Sun 15 Apr 2018 at 03:42:16 (-0700), foxfanfare wrote: > > David Wright wrote > > > It might be worth posting screenshots of Fresco failing with correctly > > > specified filenames, particularly if you want to report a bug. > > > > > > Wha

Re: \include command and local network folders

On Sun 15 Apr 2018 at 03:42:16 (-0700), foxfanfare wrote: > David Wright wrote > > It might be worth posting screenshots of Fresco failing with correctly > > specified filenames, particularly if you want to report a bug. > > > > What happens if you run your test file directly from LP, both .ly > >

Re: \include command and local network folders

David Wright wrote > It might be worth posting screenshots of Fresco failing with correctly > specified filenames, particularly if you want to report a bug. > > What happens if you run your test file directly from LP, both .ly > and .ily files—does that work correctly? If so, there may be a > prob

Re: \include command and local network folders

Il giorno gio 12 apr 2018 alle 22:42, foxfanfare ha scritto: SoundsFromSound wrote Yes, you're correct. It's a valid shared path (don't worry about the Samba share stuff). When I map drives for sharing like this, I have success using the computer name vs. the IP, for what it's worth - e

Re: \include command and local network folders

On Thu 12 Apr 2018 at 14:17:08 (-0700), foxfanfare wrote: > David Wright wrote > > Then I think that's the filename you need to use. I assume > > "Starting lilypond-windows…" means you're running on a windows box. > > Oh I see what you mean. But no! Frescobaldi starts compiling with this > Startin

Re: \include command and local network folders

David Wright wrote > Then I think that's the filename you need to use. I assume > "Starting lilypond-windows…" means you're running on a windows box. Oh I see what you mean. But no! Frescobaldi starts compiling with this Starting lilypond-windows.exe ... but I'm running on Windows 10...

Re: \include command and local network folders

On Thu 12 Apr 2018 at 12:13:21 (-0700), foxfanfare wrote: > David Wright wrote > > I see no filenames. I only see //192.168.1.13/Public/test.ly which > > looks like an incomplete URL, but lacking its protocol (like HTTP:). > > I can only assume when you mapped the files to a drive letter, > > you g

Re: \include command and local network folders

SoundsFromSound wrote > Yes, you're correct. It's a valid shared path (don't worry about the > Samba share stuff). > > When I map drives for sharing like this, I have success using the > computer name vs. the IP, for what it's worth - even though both > *should* work for all applications... >

Re: \include command and local network folders

On 4/12/2018 3:13 PM, foxfanfare wrote: David Wright wrote I see no filenames. I only see //192.168.1.13/Public/test.ly which looks like an incomplete URL, but lacking its protocol (like HTTP:). I can only assume when you mapped the files to a drive letter, you got the syntax correct. Would this

Re: \include command and local network folders

David Wright wrote > I see no filenames. I only see //192.168.1.13/Public/test.ly which > looks like an incomplete URL, but lacking its protocol (like HTTP:). > I can only assume when you mapped the files to a drive letter, > you got the syntax correct. Would this reference help? > > https://msdn.

Re: \include command and local network folders

On Thu 12 Apr 2018 at 09:32:40 (-0700), foxfanfare wrote: > Giampaolo Orrigo wrote > > I had success in doing it, but instead of using IP addresses I mapped the > > remote drive to a logical drive. Maybe you want to try that. > > > > Giampaolo Orrigo, MBA > > It worked! Thank you very much Giamp

Re: \include command and local network folders

SoundsFromSound wrote > On 4/12/2018 11:54 AM, foxfanfare wrote: > So I am very sorry for the delay. I've recorded over 20 new > videos but am still editing many of them. I hope that my tutorials can > continue to help others discover the amazing capabilities (and > community) of LilyPond - so I

Re: \include command and local network folders

On 4/12/2018 12:32 PM, foxfanfare wrote: Giampaolo Orrigo wrote I had success in doing it, but instead of using IP addresses I mapped the remote drive to a logical drive. Maybe you want to try that. Giampaolo Orrigo, MBA It worked! Thank you very much Giampaolo, problem solved! :) I don't kno

Re: \include command and local network folders

Giampaolo Orrigo wrote > I had success in doing it, but instead of using IP addresses I mapped the > remote drive to a logical drive. Maybe you want to try that. > > Giampaolo Orrigo, MBA It worked! Thank you very much Giampaolo, problem solved! :) I don't know if this "bug" come from Frescobal

Re: \include command and local network folders

On 4/12/2018 11:54 AM, foxfanfare wrote: Thanks for your answers. In fact, I just found the problem isn't due to the \include command but more in the original "ly" file that doesn't work (apparently) when it is placed on my NAS! ... even if the directory of the NAS is added in Frescobaldi. BTW

Re: \include command and local network folders

I had success in doing it, but instead of using IP addresses I mapped the remote drive to a logical drive. Maybe you want to try that. Giampaolo Orrigo, MBA > On Apr 12, 2018, at 11:54, foxfanfare wrote: > > Thanks for your answers. > > In fact, I just found the problem isn't due to the \inc

Re: \include command and local network folders

Thanks for your answers. In fact, I just found the problem isn't due to the \include command but more in the original "ly" file that doesn't work (apparently) when it is placed on my NAS! ... even if the directory of the NAS is added in Frescobaldi. For exemple: 1. I generate in Frescobaldi a ch

Re: \include command and local network folders

Try putting the style sheets files into a separate folder, e.g. C:\Users\RMY~1\LilyPond\StyleSheets Then put that path into Frescobaldi's Include window. Edit -> Preferences -> LilyPond Preferences --- Knute Snortum (via Gmail) On Thu, Apr 12, 2018 at 6:10 AM, foxfanfare wrote: > Hi everyone,

Re: \include command and local network folders

On 4/12/2018 9:10 AM, foxfanfare wrote: Hi everyone, I want to use the /include command to separate my style sheet, as suggested by some of you. I made two files : "test.ly" which contains the music, and "configuration.ily" for my house-style. The files are in the same folder and I can get it e

Re: \include command and local network folders

Am 12.04.2018 um 15:10 schrieb foxfanfare: That's odd, I don't understand why but however Lilypond seems to find my file! : That’s not LilyPond but Frescobaldi finding the file … __

\include command and local network folders

Hi everyone, I want to use the /include command to separate my style sheet, as suggested by some of you. I made two files : "test.ly" which contains the music, and "configuration.ily" for my house-style. The files are in the same folder and I can get it easily to work on my local computer drive.