Re: Installing lily 1.5.63 messes up abcm2ps

2002-06-28 Thread Mats Bengtsson
> Ok, just checked the file that .ps-file that *did not* work and with the > line out of my .bash gv shows it nicely again. So I guess the bad gyus are > lily, but who am I...? Please help us sort out this problem by checking the following: - Is $GS_LIB or $GS_FONTPATH set if you don't have lily

Re: Installing lily 1.5.63 messes up abcm2ps

2002-06-27 Thread Atte Andre Jensen
On 27 Jun 2002, Laura Conrad wrote: > I think Mats' point was to try: > > unsetenv GS_LIB > > and/or > unsetenv GS_FONTPATH > > and see which of those will cause the abcm2ps output to become > readable. I'm on my way to bed

Re: Installing lily 1.5.63 messes up abcm2ps

2002-06-27 Thread Laura Conrad
> "Atte" == Atte Andre Jensen <[EMAIL PROTECTED]> writes: Atte> Does this mean it's either/or. How about you, Laura, you run both Atte> languages on the same box, right? Yes, although I don't usually do abcm2ps. In fact, I don't seem to have abcm2ps on the machine currently. But ab

Re: Installing lily 1.5.63 messes up abcm2ps

2002-06-27 Thread Atte Andre Jensen
On Thu, 27 Jun 2002, Mats Bengtsson wrote: > I guess the culprit is the setting of the variables $GS_LIB and/or > $GS_FONTPATH in lilypond-profile, even though I can't understand > exactly what goes wrong. You're right in that... Removing the line > > . $HOME/lilypond-profile.sh from my .bashr

Re: Installing lily 1.5.63 messes up abcm2ps

2002-06-27 Thread Mats Bengtsson
I guess the culprit is the setting of the variables $GS_LIB and/or $GS_FONTPATH in lilypond-profile, even though I can't understand exactly what goes wrong. /Mats > Just installed the latest/greatest lily from source on Mandrake 8.0, but > now abcm2ps (another typesetter) doesn't work when r

Installing lily 1.5.63 messes up abcm2ps

2002-06-27 Thread Atte Andre Jensen
Just installed the latest/greatest lily from source on Mandrake 8.0, but now abcm2ps (another typesetter) doesn't work when run with my format-description. To be more precise the outputted file is not understood by neither gv or gimp. Such a problematic postscript file that is currently unreadable