On Tue, Mar 17, 2020 at 6:48 PM Marnen Laibow-Koser <mar...@marnen.org> wrote:
> On Tue, Mar 17, 2020 at 6:43 PM Arle Lommel <arle.lom...@gmail.com> wrote: > >> Glad my feedback seems to be useful. >> >> [cutting a bit here] >> >> Thanks, this makes sense. I should be able to set the variables >> correctly (and actually, the lilypond "binary" in the app bundle is already >> a script that sets a few variables and calls the real executable, so >> putting a few more in there should not be a problem). >> >> I've created https://gitlab.com/marnen/lilypond-mac-builder/-/issues/23 for >> this bug. Feel free to subscribe there for updates, or to create new >> issues there if they're problems with the 64-bit Mac packaging rather than >> LilyPond itself. >> >> >> Great. Glad it seems solvable. >> > > Yeah, if it's just a question of setting a few variables, it shouldn't be > too hard to fix. > ...but that isn't the case. Setting those variables (which were actually already set in my shell anyway) appears to have no effect. Moreover, it's only GhostScript choking on these filenames, not LilyPond. See the GitLab issue for more. Best, -- Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org
