----- Original Message -----
From: "David Kastrup" <[email protected]>
To: "James Lowe" <[email protected]>
Cc: "Phil Holmes" <[email protected]>; <[email protected]>
Sent: Tuesday, May 26, 2015 9:02 AM
Subject: Re: PDF is broken for @notation{} encoding
James Lowe <[email protected]> writes:
On 26/05/15 08:35, David Kastrup wrote:
James Lowe <[email protected]> writes:
On 25/05/15 16:08, Phil Holmes wrote:
I can try again, but it was consistent. James might want to try?
If it helps.
I get the same thing too.
How much effort is it to do one iteration on one affected file? I have
absolutely no clue how this may come about so if one could figure out
_which_ of the added defines is responsible, it might help boiling this
down. One can probably do some sort of manual bisection on the added
commands but it would still require something like 7 runs.
I don't really have any experience with 'bisections' so if you can give
me some relatively simple instructions, I don't mind doing the gruntwork
building doc over and over.
Oh, I was not talking about "git bisect". I was talking about figuring
out manually which of definitions was at fault here. The whole diff is
I'll do this later today.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
