On Sun, Mar 20, 2011 at 10:59 PM, Han-Wen Nienhuys wrote:
> On Sun, Mar 20, 2011 at 8:41 AM, wrote:
>> Reviewers: ,
>>
>> Message:
>> Hey all,
>>
>> A bug just hit the French list. It seems like a critical regression.
>>
>
> Hi,
>
> There is not much else we can do: the suggestion accidental us
On 11-03-20 05:41 AM, mts...@gmail.com wrote:
Reviewers: ,
Message:
Hey all,
A bug just hit the French list. It seems like a critical regression.
\score { %avec "surcharge" des ligatures double croches
allongées
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 [
On Sun, Mar 20, 2011 at 8:41 AM, wrote:
> Reviewers: ,
>
> Message:
> Hey all,
>
> A bug just hit the French list. It seems like a critical regression.
>
Hi,
There is not much else we can do: the suggestion accidental uses the
stem extent to determine Y positions, but that requires formatting
http://codereview.appspot.com/4289057/diff/1/Documentation/usage/lilypond-book.itely
File Documentation/usage/lilypond-book.itely (right):
http://codereview.appspot.com/4289057/diff/1/Documentation/usage/lilypond-book.itely#newcode607
Documentation/usage/lilypond-book.itely:607: @code{'landscape
http://codereview.appspot.com/4289057
Doc: Added new option 'papersize' to Usage
Added note on how to use @lilypond[papersize=xx] as defined
in scm/paper.scm
---
Hope this is in the appropriate place.
James
___
lilypond-devel mailing list
lilypon
Hello,
I can't build darwin-x86::cross/gcc with GUB.
The logfiles were too big, I have pastebinned them:
config.log: http://www.nilsgey.de/config.log
gcc.log (3.8 MB): http://www.nilsgey.de/gcc.log
I hope you can help me.
Greetings,
Nils
P.S.
This is maybe a false path. I once updated to a n
Looks generally good to me.
http://codereview.appspot.com/4277067/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4277067/diff/1/Documentation/notation/input.itely#newcode1690
Documentation/notation/input.itely:1690: more
Hey guys,
I've been busy/distracted/sick for the past week, and I'll
continue to be busy/distracted/sick for the next ten days. I'm
also fed up with announcing a release candidate and then
discovering that there's a known critical issue that wasn't on the
tracker a day later.
1) if you're worki
This is now fully functional.
The only issue is that, for auto-beams, I don't have a good method yet
for keeping note-heads that are part of the beam out of the covered
grobs list. This is doable, though - I just have to think of the
cleanest way.
http://codereview.appspot.com/4287061/
Reviewers: ,
Message:
Hey all,
A bug just hit the French list. It seems like a critical regression.
\score { %avec "surcharge" des ligatures double croches
allongées
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 [ g'8 ] a'8 [ g'8 a'16 g'16 fis'!16 e'16 ]
If I did it well, here is it: http://codereview.appspot.com/4277067
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Keith OHara schreef op vr 18-03-2011 om 21:30 [-0700]:
> The code seems to work, but requires great effort to understand.
Good, yes alas.
> I was suggesting that, having decided what you want in the MIDI, you
> might simplify the design.
That would be nice and I'm sure that it can be simplified
On Sun, 20 Mar 2011 00:17:48 -0700, Joe Neeman wrote:
On Sat, Mar 19, 2011 at 11:58 PM, wrote:
In that case, is there any need to set after_affinity at all?
I could ask the author of the original code the same question :)
I think yes. As commentary.
It assures the reader that LilyPond is p
On Sat, Mar 19, 2011 at 11:58 PM, wrote:
> On 2011/03/20 05:46:51, joeneeman wrote:
>
>> This can be fixed by adding
>> if (!pure)
>>
>
> Thanks very much.
>
> Just in case anybody wonders, we can safely put the assignment to
> after_affinity inside the if (!pure) with no change, because that
>
14 matches
Mail list logo
