Re: [PATCH] More bugfixes

[Juergen Reuter]

On Thu, 28 Feb 2002, Han-Wen Nienhuys wrote:

> address@hidden writes:
> > Though I have attached some more bugfixes, just for the record (also for
> > myself to remind), here are some more open issues:
> >
> > * output-lib.scm, function find-notehead-symbol:
> >   often switches between note heads of different font-families
> >   (e.g. baroque: optionally select (neo_)mensural note heads), which
> >   will not work (unless font-family is automatically changed).
> >   Possible solution 1: move neo_mensural stuff from parmesan to feta
> >   Possible solution 2: in find-notehead-symbol, also include font-family
>
> I don't like 1. , since it means that we have to overcrowd the feta
> font again when we add more notation symbols. So I'd vote for 2.
>

Possible solution 3: Defer this problem until we have agreed on a
general solution for font mapping.  Then this issue will probably become
trivial.

> > * segmentation fault (in 1.5.33; I actually didn't check this in 1.5.34):
>
> Which file caused this ?
>

input/test/ancient-font.ly.  Meanwhile, I checked it for .34, and it's
still there.  Since I have not installed .35 or .36, I do not know if it's
in these releases.

> > * N.B.: To get this (still too short or maybe even corrupted?)
> >   backtrace, I had to run lilypond from the lily/out directory, since
> >   debugging symbols were stripped off when doing "make install",
> >   although --enable-debugging had been set.  Is this intended
> >   behaviour?
>
> Hrm... never thought of this. We developers always run LilyPond from
> the source directory.
>

Maybe I am a little bit paranoid, but for testing purposes, I usually
create a separate install directory for each version (with a symbolic link
pointing to this directory, and /usr/bin/lilypond etc. pointing to below
this link, so that I only have to change this single link and doing a
rehash on the shell for switching to a different version of lilypond).

Greetings,
Juergen