Hi Urs, thanks for the fix. Files compile fine now. However, now I get these warnings:
Parsing... openLilyLib: library infrastructure successfully loaded. /[$HOME]/[$Docs]/openlilylib.ily:4:1: warning: openLilyLib: Library main file "/[$HOME]/.lilypond/openlilylib/ly/scholarly/__main__.ily" not found \useLibrary Scholarly /[$HOME]/.lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:50:1: warning: openLilyLib: Library main file "/[$HOME]/.lilypond/openlilylib/ly/utility/__main__.ily" not found \useLibrary utility /[$HOME]/.lilypond/openlilylib/ly/scholarly/annotate/__main__.ily:51:1: warning: openLilyLib: Module already loaded. Skipping "utility.rhythmic-location" \useModule utility.rhythmic-location Interpreting music... so … some directories still need cleaning up a bit, yes? Cheers, A On Tue, Jul 7, 2015 at 5:21 PM, Urs Liska <u...@openlilylib.org> wrote: > For all users of openLilyLib, > > I have hopefully fixed this issue. > At least as far as the "new" openLilyLib infrastructure (i.e. the > \include "openlilylib" > approach) is concerned and is covered by our automated test suite (thank > you Matteo, this proves to be a really valuable resource). > > That means: > If you use functionality from inside the "new" openLilyLib you should be > able to compile it with LilyPond less-than, equal or greater-than > 2.19.22 again. > > I can't tell about the stuff that is in the "old" snippets' directories. > Probably there will be more to iron out in the future, latest if we > start migrating the contents to the new structure. But as it mainly > affects ly:parser-lookup and ly:parser-define! I don't expect too many > issues to come up. > > But for anybody: If you encounter errors indicating wrong numbers of > arguments and pointing inside openLilyLib please open issues or ask on > lilypond-user. > > Best > Urs > > > Am 29.06.2015 um 22:23 schrieb N. Andrew Walsh: > > Bug report added: > > > > https://github.com/openlilylib/openlilylib/issues/125 > > > > Cheers, > > > > A > > > > On Sat, Jun 27, 2015 at 11:48 AM, Urs Liska <u...@openlilylib.org > > <mailto:u...@openlilylib.org>> wrote: > > > > > > > > Am 27.06.2015 um 11:22 schrieb N. Andrew Walsh: > > > Hi Urs, > > > > > > My desktop is a gentoo system which builds directly from the git > > > repository (gentoo has something like a "live" package, with a > version > > > number -9999 at the end, that pulls from the live branch). On my > sytem, > > > that returns a lily version of 2.19.22. > > > > Oh, interesting. > > > > > My laptop, however, is an ubuntu > > > system (never managed to get gentoo working on it, alas!), for > which I > > > have 2.19.21 installed from the .sh file available on the website. > > > > > > So, it's probably the case that whatever the issue is will come up > again > > > when I get home. > > > > Surely. > > > > > If it's any help, a lot of my system fonts now appear > > > much sharper (say, in the file manager, or Firefox), which I > suspect has > > > to do with a recent update to one of the base packages. I'll let > you > > > know when I get home. > > > > > > Thanks for the help. > > > > > > > Could you please add an issue to > > https://github.com/openlilylib/openlilylib/issues > > > > Best > > Urs > > > > > A > > > > > > On Sat, Jun 27, 2015 at 11:16 AM, Urs Liska <u...@openlilylib.org > <mailto:u...@openlilylib.org> > > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org>>> wrote: > > > > > > > > > > > > Am 27.06.2015 um 11:04 schrieb N. Andrew Walsh: > > > > Well, I've now loaded this up on my laptop, and re-cloned the > > > > openlilylib directory, and now the problem no longer > appears. I have > > > > other issues -- namely that my production box is running > lilypond > > > > 2.19.22, which I can't seem to install from ubuntu -- but > those are minor. > > > > > > 2.19.22 isn't released yet AFAICS. Do you have a custom built > LilyPond? > > > > > > > > > > > Urs, did you update something on the git tree, or was this > simply a > > > > problem on my side that I'll run into again when I get back > home? > > > > > > It's not clear what you say. Do you have a laptop with > something < > > > 2.19.22 and a home pc with a custom build from the 2.19.22 > line? > > > > > > If that's the case then probably you'll experience the problem > at home > > > again because the changes in LilyPond have been introduced > there. > > > > > > I assume I'll have to change the implementation (and look for > other > > > parts where this might matter) and introduce a version switch > so the > > > code executed from openLilyLib depends on the LilyPond version. > > > > > > I'm approaching the state to be able to work properly again. > > > Unfortunately I have to pick up a presentation for upcoming > Wednesday. > > > Anyone in or near Karlsruhe BTW? > > > > > > Urs > > > > > > > > > > > Cheers, > > > > > > > > A > > > > > > > > On Sat, Jun 27, 2015 at 12:05 AM, Urs Liska < > u...@openlilylib.org <mailto:u...@openlilylib.org> > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org>> > > > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org> > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org>>>> wrote: > > > > > > > > > > > > > > > > Am 26.06.2015 um 23:50 schrieb David Kastrup: > > > > > Urs Liska <u...@openlilylib.org <mailto: > u...@openlilylib.org> > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org>> > > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org> > > <mailto:u...@openlilylib.org <mailto:u...@openlilylib.org>>>> writes: > > > > > > > > > >> Oh, I didn't realize this might be for me... > > > > >> I'll try to look into it ASAP. But at the moment I > don't have a > > > > >> working LilyPond at hand. > > > > >> > > > > >> I have some ideas, though. Maybe openlilylib has to > be adapted to a > > > > >> recent LilyPond improvement. > > > > > > > > > > Well, it's probably most reliable if your installation > instructions > > > > > and/or scripts include a run of convert-ly. > Otherwise, there will be > > > > > unhappy people with either variant for a long time. > > > > > > > > I think in the case of openLilyLib I will manually > update the code and > > > > include a version switch. openLilyLib should in general > work with all > > > > versions at least since the latest stable release. > > > > > > > > Users should not do any update/convert-ly themselves, > they rather > > > > download or 'git pull' updated versions of the library. > > > > > > > > Urs > > > > > > > > > > > > _______________________________________________ > > > > lilypond-user mailing list > > > > lilypond-user@gnu.org <mailto:lilypond-user@gnu.org> > > <mailto:lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>> > > > <mailto:lilypond-user@gnu.org <mailto:lilypond-user@gnu.org> > > <mailto:lilypond-user@gnu.org <mailto:lilypond-user@gnu.org>>> > > > > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > > > > > > > > > > > > > > > > >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
