http://codereview.appspot.com/2275042/diff/2001/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (right):
http://codereview.appspot.com/2275042/diff/2001/scm/define-markup-commands.scm#newcode3375
scm/define-markup-commands.scm:3375: (number? number? markup?)
Hi Neil, your patc
The commit mentioned in the subject line is just not right. The purpose
of a definition like "define-event-class" is not, as far as I am
concerned, to provide an attack vector where one can, given suitable
ingenuity, hack together code that fiddles with internals to the effect
of defining an even
Dear all,
when using the current Lilypond.app (2.13.35-1 and the stable one),
Point-and-Click will work out-of-the-box for the Mac - nice. But there is no
recipe on what to do if you prefer not to use the builtin text editor.
However, there is a solution for the Mac: distributed with lyqi by Ni
In short: great work, push it. Two slight remarks on skylines (I prefer
the wording in your answer on my post), and perhaps about Hooke's law.
But I don't have a strong point on the latter.
On 2010/10/02 16:09:22, Mark Polesky wrote:
Documentation/notation/spacing.itely:200: @table @code
On 20
Is this a good change?
Cheers,
- Graham
From f021b1f3fa3a696a132dcdd6e27005c95e27176f Mon Sep 17 00:00:00 2001
From: Graham Percival
Date: Mon, 4 Oct 2010 18:16:40 +0100
Subject: [PATCH] Doc: update accordion glyphs.
---
Documentation/notation/text.itely |8
1 files changed, 4 inse
convert-ly complains about the woodwind diagrams in wind.itely.
- if the current material is correct, please bump the
@c \version "2.12.0"
at the top of the file to 2.13.36
- if it's not correct, fix the woodwind diagrams, then bump the version number.
Cheers,
- Graham
__
Graham Percival writes:
> Is this a good change?
>
> Cheers,
> - Graham
> From f021b1f3fa3a696a132dcdd6e27005c95e27176f Mon Sep 17 00:00:00 2001
Should think so. How did I overlook that?
--
David Kastrup
___
lilypond-devel mailing list
lilypond-de
The old convert-ly complains about things like \bar "'" but
judging from the warning message, it's only supposed to match
\bar "."
Does this patch look ok?
Cheers,
- Graham
From ea112d150717319f2592dc417b73d0ffe9e54a80 Mon Sep 17 00:00:00 2001
From: Graham Percival
Date: Mon, 4 Oct 2010 18:25:10
On Mon, Oct 4, 2010 at 6:24 PM, David Kastrup wrote:
> Graham Percival writes:
>
>> Is this a good change?
>>
>> Cheers,
>> - Graham
>> From f021b1f3fa3a696a132dcdd6e27005c95e27176f Mon Sep 17 00:00:00 2001
>
> Should think so. How did I overlook that?
Judging from the version strings, nobody's
On 10/4/10 11:21 AM, "Graham Percival" wrote:
> convert-ly complains about the woodwind diagrams in wind.itely.
> - if the current material is correct, please bump the
> @c \version "2.12.0"
> at the top of the file to 2.13.36
The current version is correct. We didn't update to 2.13.36 becau
On 10/4/10 11:18 AM, "Graham Percival" wrote:
> Is this a good change?
Yes. convert-ly should have made these changes automatically, I think.
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listi
Graham Percival writes:
> On Mon, Oct 4, 2010 at 6:24 PM, David Kastrup wrote:
>> Graham Percival writes:
>>
>>> Is this a good change?
>>>
>>> Cheers,
>>> - Graham
>>> From f021b1f3fa3a696a132dcdd6e27005c95e27176f Mon Sep 17 00:00:00 2001
>>
>> Should think so. How did I overlook that?
>
> Ju
Could somebody who's read the spacing docs fix these?
gperc...@gperciva-desktop:~/src/lilypond/Documentation/notation$ git
grep minimum-Y-extent
ancient.itely: \override VerticalAxisGroup #'minimum-Y-extent = ##f
ancient.itely: \override VerticalAxisGroup #'minimum-Y-extent = ##f
percuss
On Mon, Oct 4, 2010 at 6:30 PM, David Kastrup wrote:
> Ah, I think I remember that somebody told me that the important thing
> was the convert-ly rule, and that the automatic procedures would take
> care of the rest.
That makes sense. Yes, those changes came from convert-ly. I'll push it soon.
On Mon, Oct 4, 2010 at 6:29 PM, Carl Sorensen wrote:
>
> The current version is correct. We didn't update to 2.13.36 because we
> hadn't run convert-ly on the whole file.
Thanks, pushed.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel
Usually when I propose things like this, they're shot down
pretty fast, but here goes anyway.
It took me a while to mentally connect the names of the
vertical spacing variables with their specific domains. For
example, I think it's counterintuitive that
'after-title-spacing does *not* affect the
Mark Polesky wrote Monday, October 04, 2010 11:14 PM
Usually when I propose things like this, they're shot down
pretty fast, but here goes anyway.
It took me a while to mentally connect the names of the
vertical spacing variables with their specific domains. For
example, I think it's counter
Dear documentation editors,
In the existing @knownissues for cadenzaOn, I suggest adding one sentence (in
context below) encouraging manual beams. Users might *think* autobeaming works
through cadenzas, and it does for a while, but it will not through longer
cadenzas.
There is a related lo
18 matches
Mail list logo
