Folks,
why are variable assignments not allowed in \bookpart? For example,
this snippet
\bookpart {
APT = \allowPageTurn
{ c'' }
}
fails. In case this is just an omission, can it be fixed easily?
Werner
___
lilypond-devel mailin
Am 09.02.2015 um 09:31 schrieb Werner LEMBERG:
Folks,
why are variable assignments not allowed in \bookpart? For example,
this snippet
\bookpart {
APT = \allowPageTurn
{ c'' }
}
fails. In case this is just an omission, can it be fixed easily?
If not this should help you
Werner LEMBERG writes:
> Folks,
>
>
> why are variable assignments not allowed in \bookpart? For example,
> this snippet
>
> \bookpart {
> APT = \allowPageTurn
>
> { c'' }
> }
>
> fails. In case this is just an omission, can it be fixed easily?
Well, as far as I can see, assignment
Am 2015-02-09 um 01:34 schrieb Edward d'Auvergne :
> I was wondering what the current status of Guile 2 support in Lilypond
> is? The dev/guilev2 branch hasn't been touched since 2014-10-13. It
> is becoming more and more impossible to run Lilypond on modern Linux
> distributions (for example se
"Edward d'Auvergne" writes:
> Hi,
>
> I was wondering what the current status of Guile 2 support in Lilypond
> is? The dev/guilev2 branch hasn't been touched since 2014-10-13.
That corresponds with the last time I got a promise GUILEv2 developers
would take a look at our GC problems.
> It is b
Folks,
consider the following snippet.
#(set-default-paper-size "a6")
\paper {
systems-per-page = 6
blank-page-penalty = 1000
#(define page-breaking ly:page-turn-breaking)
copyright = ""
footer = ""
tagline = ""
}
m = \relative c' {
f'8 f, f f f f f f
>> why are variable assignments not allowed in \bookpart? [...]
>
> Well, as far as I can see, assignments are also not allowed in
> books.
Hmm...
> And the reason mostly would be that books and bookparts don't have
> scope of their own (apart from book's \paper block). So even if it
> were all
Werner LEMBERG writes:
>>> why are variable assignments not allowed in \bookpart? [...]
>>
>> Well, as far as I can see, assignments are also not allowed in
>> books.
>
> Hmm...
>
>> And the reason mostly would be that books and bookparts don't have
>> scope of their own (apart from book's \pape
> Here is an example (where I use the Scheme equivalent of
> assignment): [...]
Interesting. Note that
foo = \relative c' { c d e f g }
\bookpart {
\foo
}
foo = \relative c'' { g f e d c }
\bookpart {
\foo
}
fortunately works as expected (this is, different notes in differ
Werner LEMBERG writes:
>> Here is an example (where I use the Scheme equivalent of
>> assignment): [...]
>
> Interesting. Note that
>
> foo = \relative c' { c d e f g }
> \bookpart {
> \foo
> }
>
> foo = \relative c'' { g f e d c }
> \bookpart {
> \foo
> }
>
> fortunately wor
On 09/02/15 10:19, Werner LEMBERG wrote:
> consider the following snippet.
>
> #(set-default-paper-size "a6")
>
> \paper { systems-per-page = 6 blank-page-penalty = 1000
>
> #(define page-breaking ly:page-turn-breaking)
>
> copyright = "" footer = "" tagline = "" }
>
> m = \relative c' { f'8 f
>> So I think that your comparison is not completely valid, since
>> lilypond's `variables' are obviously expanded at a different time
>> than Scheme assignments.
>
> No, they aren't. This is not due to a difference between LilyPond
> and Scheme. If you override with #notecolor you'll again get
Werner LEMBERG writes:
>> We don't allow assignments inside of music expressions either, and
>> again the reason is not as much that it wouldn't be possible to
>> allow them there, but rather that people would be surprised that
>> "reassigning" a variable inside of music will affect previous uses
> Maybe I'm being a bit hasty but
>
> https://code.google.com/p/lilypond/issues/detail?id=4285
Thanks. It perhaps makes sense to add the PDF file also...
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman
LGTM
https://codereview.appspot.com/201140043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2015/02/09 06:09:34, lemzwerg wrote:
LGTM. It would be nice if David's checker script could be added, too.
More, I'd consider it a good idea to use the checker on the current
patch again.
There was such a mess that I'm not sure I corrected all.
https://codereview.appspot.com/199460043/di
Reviewers: ,
Message:
Just fixing a typo on the website.
-Paul
Description:
Web: introduction.itexi fix typo (Vim -> Emacs)
Please review this at https://codereview.appspot.com/197530043/
Affected files (+1, -1 lines):
M Documentation/web/introduction.itexi
Index: Documentation/web/introdu
Reviewers: ,
Message:
Please review, thanks.
Description:
Web: CSS: remove vendor prefixed border-radius
No need for these anymore:
-moz-border-radius
-webkit-border-radius
Please review this at https://codereview.appspot.com/200340043/
Affected files (+2, -24 lines):
M Documentation/css/li
18 matches
Mail list logo
