bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug: font caching on OS X w/ networked home folders


From: Jacob Rundall
Subject: Re: Bug: font caching on OS X w/ networked home folders
Date: Mon, 14 Dec 2009 19:49:22 -0600

It's not a problem for me to keep testing as I'm an administrator of two Mac
labs with networked homefolders.  I've been away from work for a few days
but I'll be there tomorrow morning.  I'll test with 2.13.9-1 and if anybody
has a working link for a newer version I'll try that too.

As I mentioned in the report, the .lilypond-fonts.cache-2 directory is
created successfully, but not filled.  So I wonder if the code that creates
the cache files is trying to reach the homefolder by a different method (ie
assuming homefolders are only located in /Users for example).

Thanks for looking into this.

Jake

On Fri, Dec 11, 2009 at 10:19 PM, Patrick McCarty <address@hidden> wrote:

> On Fri, Dec 11, 2009 at 11:22 AM, Carl Sorensen <address@hidden>
> wrote:
> >
> > On 12/11/09 12:00 PM, "Valentin Villenave" <address@hidden>
> wrote:
> >
> >> On Tue, Dec 8, 2009 at 6:32 PM, Jake Rundall <address@hidden>
> wrote:
> >>> %% Font caching fails on OS X w/ networked homefolders,
> >>>
> >>> %% The .lilypond-fonts.cache-2 directory is created in the user's home
> >>> directory,
> >>> %% but the cache files do not show up there.  Performance is always
> very slow
> >>> as
> >>> a result.
> >>
> >> could you try again with the latest version that's just been released?
> >>
> http://kainhofer.com/~lilypond/Documentation/web/development.html#Development
> >>
> >> I can't reproduce it since I don't have an OSX box; Patrick, could you
> >> investigate when you have time?
> >
> > This may be a very difficult bug to reproduce, since it requires OSX with
> > "networked homefolders", which I assume means a user with a home folder
> that
> > resides on a network drive.
>
> I can only login to OSX machines with local home folders, so I don't
> think I will be able to test this.
>
> -Patrick
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]