On May 28, 2011, at 2:28 PM, carl.d.soren...@gmail.com wrote:
> Do we need to change the definition of stem-attachment in
> scm/define-grobs.scm to be ,boolean-or-number-pair? (and maybe define a
> new ,boolean-or-number-pair predicate)?
>
To my knowledge, #f can be used for all properties. So
2011/5/30 Phil Holmes :
> For those who are
> interested in the build system, I attach my notes to date of how make doc
> works - slightly stream-of-consciousness, I'm afraid.
>git/build/input/GNUmakefile is:
>depth=../
This should be 'depth=..' without the trailing '/'
>include $(depth)/confi
On May 31, 2011, at 6:23 AM, Werner LEMBERG wrote:
>> I've been getting this from LilyPond recently:
>>
>> programming error: Parsed object should be dead: static scm_unused_struct*
>> Prob::mark_smob(scm_unused_struct*)
>> continuing, cross fingers
>>
>> Is anyone else getting this too?
>
> I
> I've been getting this from LilyPond recently:
>
> programming error: Parsed object should be dead: static scm_unused_struct*
> Prob::mark_smob(scm_unused_struct*)
> continuing, cross fingers
>
> Is anyone else getting this too?
I'm getting this all the time if I build with --disable-optimisi
Hey all,
I've been getting this from LilyPond recently:
programming error: Parsed object should be dead: static scm_unused_struct*
Prob::mark_smob(scm_unused_struct*)
continuing, cross fingers
Is anyone else getting this too?
Cheers,
MS
___
lilypon
On Mon, May 30, 2011 at 07:54:14PM +0100, Graham Percival wrote:
> Could somebody look at stable/2.14 and identify whatever extra
> commit(s) are requried to make it compile
> input/regression/page-spacing-bass-figures.ly
> ? currently it fails.
sorry, ignore that -- the problem was the \versio
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Carl Sorensen" ;
Sent: Saturday, May 28, 2011 6:22 PM
Subject: Re: make doc
On Sat, May 28, 2011 at 05:48:39PM +0100, Phil Holmes wrote:
So the command line would need to be something like
lilypond filename.ly > f
Could somebody look at stable/2.14 and identify whatever extra
commit(s) are requried to make it compile
input/regression/page-spacing-bass-figures.ly
? currently it fails.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https
Reviewers: ,
Message:
I believe this new version of the glissando line breaking patch responds
to Keith's concern.
Please let me know what you think!
Cheers,
MS
Description:
Implements multiple-line non-cross-staff glissandi
Please review this at http://codereview.appspot.com/4527086/
Affect
LGTM
Carl
http://codereview.appspot.com/4490045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/4490045/diff/12001/lily/completion-note-heads-engraver.cc
File lily/completion-note-heads-engraver.cc (right):
http://codereview.appspot.com/4490045/diff/12001/lily/completion-note-heads-engraver.cc#newcode207
lily/completion-note-heads-engraver.cc:207:
event->set_p
On 2011/05/29 18:36:20, Janek Warchol wrote:
New patch set from Karin uploaded.
thanks, looks marvelous to me.
Pal
http://codereview.appspot.com/4490045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/
New patch set from Karin uploaded.
http://codereview.appspot.com/4490045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 5/30/11 3:46 AM, "Jan Nieuwenhuizen" wrote:
>
>> Actually, the last patch than Jan posted should make LilyPond work on
>> windows 7 sp1, IIUC. So as long as we backport that patch, we're good with
>> windows.
>
> Indeed! Ghostscript 9.0 is not required, neither is freetype 2.4.4 --
> bu
longest-church-rest is the longest rest displayed in church rests.
One may want to only print a whole rest in a breve measure but print
breve and longa rests in a church rest.
But I agree with you, it can be changed for the min value of
usable-duration-logs.
You're right for measure-duration-log.
Carl Sorensen writes:
>> I think the best thing is to get 2.14.0 out now, include a warning
>> that it doesn't work on windows 7 SP1 but that we're testing a fix
>> and hope to have a new version out soon. Then we switch to
>> ghostscript-9.0 in 2.15.0 and start testing.
Sure, however/or esp. as
On May 30, 2011, at 12:20 AM, k-ohara5...@oco.net wrote:
> This fails the "sniff test" because it removes some careful-looking code
> no explanation as to how the job of the old code is being done.
>
> What happens if the line on the next page is does not, in fact, have the
> same vertical refere
17 matches
Mail list logo
