Re: openLilyLib and the 'parser' update (was: garbled output, error)
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 - 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
openLilyLib and the 'parser' update (was: garbled output, error)
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 - 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,
Re: garbled output, error
Am 29.06.2015 um 22:23 schrieb N. Andrew Walsh: Bug report added: https://github.com/openlilylib/openlilylib/issues/125 Cheers, A Thanks, I was already on my way shifting that issue out of focus ;-) Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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 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 - 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 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 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 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 https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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 - at the end, that pulls from the live branch). On my sytem, that returns a lily version of 2.19.22. 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. 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. A On Sat, Jun 27, 2015 at 11:16 AM, Urs Liska 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 wrote: Am 26.06.2015 um 23:50 schrieb David Kastrup: Urs Liska 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 https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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 - 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 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 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 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 https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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. 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? Cheers, A On Sat, Jun 27, 2015 at 12:05 AM, Urs Liska u...@openlilylib.org wrote: Am 26.06.2015 um 23:50 schrieb David Kastrup: Urs Liska 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 https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
Urs Liska u...@openlilylib.org writes: 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. Unfortunately, 2.19.22 has not yet been released so there is 2.19.22 before change and 2.19.22 after change rather than 2.19.22 at the point of its release. It might be more reliable to use something like (catch 'wrong-number-of-args (lambda () (something bla)) (lambda _ (something parser bla))) which just tries the new calling convention and, failing that, reverts to the old call. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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 wrote: Am 26.06.2015 um 23:50 schrieb David Kastrup: Urs Liska 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 https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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 - 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 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 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 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 https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
Am 27.06.2015 um 11:34 schrieb David Kastrup: Urs Liska u...@openlilylib.org writes: 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. Unfortunately, 2.19.22 has not yet been released so there is 2.19.22 before change and 2.19.22 after change rather than 2.19.22 at the point of its release. It might be more reliable to use something like (catch 'wrong-number-of-args (lambda () (something bla)) (lambda _ (something parser bla))) which just tries the new calling convention and, failing that, reverts to the old call. That's surely cleaner. But I'll stick to my simpler approach because if I add this switch which will execute the new code when version = 2.19.22 this will only fail for someone who has a custom build from not the latest master. *If* someone should run in that corner case and really needs to use that functionality that person could afford pulling the latest master and building LilyPond IMO Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
Am 27.06.2015 um 11:34 schrieb David Kastrup: Urs Liska u...@openlilylib.org writes: 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. Unfortunately, 2.19.22 has not yet been released so there is 2.19.22 before change and 2.19.22 after change rather than 2.19.22 at the point of its release. It might be more reliable to use something like (catch 'wrong-number-of-args (lambda () (something bla)) (lambda _ (something parser bla))) which just tries the new calling convention and, failing that, reverts to the old call. That's surely cleaner. But I'll stick to my simpler approach because if I add this switch which will execute the new code when version = 2.19.22 this will only fail for someone who has a custom build from not the latest master. *If* someone should run in that corner case and really needs to use that functionality that person could afford pulling the latest master and building LilyPond IMO Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
Andrew, Looks like you need to go into the file /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib and change the line (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\) to (ly:parser-include-string \\include \_internal/init-openlilylib.ily\) (i.e., remove the parser argument). See if that helps. There could be more to it than that, but that might at least get you past this error. - Abraham On Fri, Jun 26, 2015 at 2:30 PM, N. Andrew Walsh [via Lilypond] ml-node+s1069038n178240...@n5.nabble.com wrote: I had the message below rejected, because the pdf output was too large for the list (though 400k seems not that large these days; maybe that's wrong?). Anyway, can anybody help with the errors I'm getting? I can send the pdf privately, if anybody's interested. Cheers, A -- Forwarded message -- From: N. Andrew Walsh [hidden email] http:///user/SendEmail.jtp?type=nodenode=178240i=0 Date: Jun 26, 2015 3:41 PM Subject: garbled output, error To: lilypond-user [hidden email] http:///user/SendEmail.jtp?type=nodenode=178240i=1 Cc: I would normally submit this to a bug list, but this deals with openlilylib, so I'm not sure where to send it. Anyway, I have some system updates between now and my last use of Lily. When I tried again today, two things happened: first, the first PDF output made all the text parts (dynamics, titles, time signatures, etc) *huge* (see attached file. Second, when I updated Lily and Frescobaldi, I got this error: Starting lilypond 2.19.22 [transkription kayser psalmi in vesperas.ly]... Processing `/home/[$HOME]/transkription kayser/psalmi in vesperas/transkription kayser psalmi in vesperas.ly' Parsing.../home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://0: In procedure ly:parser-include-string in expression (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\): /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://1: Wrong number of arguments to #primitive-procedure ly:parser-include-string Exited with return code 1. Whoops? Any advice on what's going wrong? Is the former a more normal bug that I should submit to the bug-list? Is the latter something about recent openlilylib that might cause issues? Cheers, A ___ lilypond-user mailing list [hidden email] http:///user/SendEmail.jtp?type=nodenode=178240i=2 https://lists.gnu.org/mailman/listinfo/lilypond-user -- If you reply to this email, your message will be added to the discussion below: http://lilypond.1069038.n5.nabble.com/Fwd-garbled-output-error-tp178240.html To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com To unsubscribe from Lilypond, click here http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=2code=dGlzaW1zdC5saWx5cG9uZEBnbWFpbC5jb218Mnw4MzU3Njg3MDU= . NAML http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://lilypond.1069038.n5.nabble.com/Fwd-garbled-output-error-tp178240p178242.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fwd: garbled output, error
N. Andrew Walsh n.andrew.wa...@gmail.com writes: I had the message below rejected, because the pdf output was too large for the list (though 400k seems not that large these days; maybe that's wrong?). Anyway, can anybody help with the errors I'm getting? I can send the pdf privately, if anybody's interested. [...] Starting lilypond 2.19.22 [transkription kayser psalmi in vesperas.ly]... Processing `/home/[$HOME]/transkription kayser/psalmi in vesperas/transkription kayser psalmi in vesperas.ly' Parsing.../home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://0: In procedure ly:parser-include-string in expression (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\): /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://1: Wrong number of arguments to #primitive-procedure ly:parser-include-string Exited with return code 1. Whoops? Any advice on what's going wrong? Is the former a more normal bug that I should submit to the bug-list? Is the latter something about recent openlilylib that might cause issues? Change in LilyPond. Try running convert-ly -ed on the file in question. If it has a proper \version header pointing to the correct version (namely a version _before_ 2.19.22), you have a rather good chance that the upgrade to version 2.19.22 that convert-ly performs will do the trick. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
tisimst tisimst.lilyp...@gmail.com writes: Andrew, Looks like you need to go into the file /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib and change the line (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\) to (ly:parser-include-string \\include \_internal/init-openlilylib.ily\) (i.e., remove the parser argument). See if that helps. There could be more to it than that, but that might at least get you past this error. It's better to let convert-ly do the work rather than try to edit everything by hand. Even if it is just to give me the impression that the days I spend on devising a working convert-ly rule for complex conversions are not a waste of time. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
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. Urs Am 26. Juni 2015 23:20:32 MESZ, schrieb tisimst tisimst.lilyp...@gmail.com: Andrew, Looks like you need to go into the file /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib and change the line (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\) to (ly:parser-include-string \\include \_internal/init-openlilylib.ily\) (i.e., remove the parser argument). See if that helps. There could be more to it than that, but that might at least get you past this error. - Abraham On Fri, Jun 26, 2015 at 2:30 PM, N. Andrew Walsh [via Lilypond] ml-node+s1069038n178240...@n5.nabble.com wrote: I had the message below rejected, because the pdf output was too large for the list (though 400k seems not that large these days; maybe that's wrong?). Anyway, can anybody help with the errors I'm getting? I can send the pdf privately, if anybody's interested. Cheers, A -- Forwarded message -- From: N. Andrew Walsh [hidden email] http:///user/SendEmail.jtp?type=nodenode=178240i=0 Date: Jun 26, 2015 3:41 PM Subject: garbled output, error To: lilypond-user [hidden email] http:///user/SendEmail.jtp?type=nodenode=178240i=1 Cc: I would normally submit this to a bug list, but this deals with openlilylib, so I'm not sure where to send it. Anyway, I have some system updates between now and my last use of Lily. When I tried again today, two things happened: first, the first PDF output made all the text parts (dynamics, titles, time signatures, etc) *huge* (see attached file. Second, when I updated Lily and Frescobaldi, I got this error: Starting lilypond 2.19.22 [transkription kayser psalmi in vesperas.ly]... Processing `/home/[$HOME]/transkription kayser/psalmi in vesperas/transkription kayser psalmi in vesperas.ly' Parsing.../home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://0: In procedure ly:parser-include-string in expression (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\): /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://1: Wrong number of arguments to #primitive-procedure ly:parser-include-string Exited with return code 1. Whoops? Any advice on what's going wrong? Is the former a more normal bug that I should submit to the bug-list? Is the latter something about recent openlilylib that might cause issues? Cheers, A ___ lilypond-user mailing list [hidden email] http:///user/SendEmail.jtp?type=nodenode=178240i=2 https://lists.gnu.org/mailman/listinfo/lilypond-user -- If you reply to this email, your message will be added to the discussion below: http://lilypond.1069038.n5.nabble.com/Fwd-garbled-output-error-tp178240.html To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com To unsubscribe from Lilypond, click here http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=2code=dGlzaW1zdC5saWx5cG9uZEBnbWFpbC5jb218Mnw4MzU3Njg3MDU= . NAML http://lilypond.1069038.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://lilypond.1069038.n5.nabble.com/Fwd-garbled-output-error-tp178240p178242.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list 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
Re: garbled output, error
On Fri, Jun 26, 2015 at 3:31 PM, David Kastrup [via Lilypond] ml-node+s1069038n178244...@n5.nabble.com wrote: tisimst [hidden email] http:///user/SendEmail.jtp?type=nodenode=178244i=0 writes: Andrew, Looks like you need to go into the file /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib and change the line (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\) to (ly:parser-include-string \\include \_internal/init-openlilylib.ily\) (i.e., remove the parser argument). See if that helps. There could be more to it than that, but that might at least get you past this error. It's better to let convert-ly do the work rather than try to edit everything by hand. Even if it is just to give me the impression that the days I spend on devising a working convert-ly rule for complex conversions are not a waste of time. I'll +1 to that! I knew you had done a bunch of work to simplify the arguments for these kinds of functions, but I forgot about using convert-ly. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Fwd-garbled-output-error-tp178240p178246.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Fwd: garbled output, error
I had the message below rejected, because the pdf output was too large for the list (though 400k seems not that large these days; maybe that's wrong?). Anyway, can anybody help with the errors I'm getting? I can send the pdf privately, if anybody's interested. Cheers, A -- Forwarded message -- From: N. Andrew Walsh n.andrew.wa...@gmail.com Date: Jun 26, 2015 3:41 PM Subject: garbled output, error To: lilypond-user lilypond-user@gnu.org Cc: I would normally submit this to a bug list, but this deals with openlilylib, so I'm not sure where to send it. Anyway, I have some system updates between now and my last use of Lily. When I tried again today, two things happened: first, the first PDF output made all the text parts (dynamics, titles, time signatures, etc) *huge* (see attached file. Second, when I updated Lily and Frescobaldi, I got this error: Starting lilypond 2.19.22 [transkription kayser psalmi in vesperas.ly]... Processing `/home/[$HOME]/transkription kayser/psalmi in vesperas/transkription kayser psalmi in vesperas.ly' Parsing.../home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://0: In procedure ly:parser-include-string in expression (ly:parser-include-string parser \\include \_internal/init-openlilylib.ily\): /home/[$HOME]/.lilypond/openlilylib/ly/openlilylib:28:9 http://1: Wrong number of arguments to #primitive-procedure ly:parser-include-string Exited with return code 1. Whoops? Any advice on what's going wrong? Is the former a more normal bug that I should submit to the bug-list? Is the latter something about recent openlilylib that might cause issues? Cheers, A ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
Am 26.06.2015 um 23:50 schrieb David Kastrup: Urs Liska 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 https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: garbled output, error
Urs Liska 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. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
