Re: garbled output, error

[Urs Liska]

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 <address@hidden
> <mailto:address@hidden>> wrote:
> 
> 
> 
>     Am 26.06.2015 um 23:50 schrieb David Kastrup:
>     > Urs Liska <address@hidden <mailto:address@hidden>> 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
>     address@hidden <mailto:address@hidden>
>     https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
>