Paul Morris wrote
> Looks like the following works. I just added a second argument to the
> lambda expression. It is just ignored, but it prevents the error.
> (n) -> (n x)
>
> \layout {
> \context {
> \Score
> barNumberVisibility = #all-bar-numbers-visible
> barNumberVisibility
James writes:
> On 06/01/14 20:47, Federico Bruni wrote:
>> 2014/1/6 Esa Erola
>>
>>>
>>> The snippet putting bar numbers on odd bars does not seem to work on 2.16.0
>>> - it worked on an earlier release
>>>
>>>
>>> \context {
>>> \Score
>>> barNumberVisibility = #all-bar-numbers-visib
Looks like the following works. I just added a second argument to the lambda
expression. It is just ignored, but it prevents the error.
(n) -> (n x)
HTH,
-Paul
\version "2.18.0"
\layout {
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
barNumberVisibility = #(
On 06/01/14 20:47, Federico Bruni wrote:
2014/1/6 Esa Erola
The snippet putting bar numbers on odd bars does not seem to work on 2.16.0
- it worked on an earlier release
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
barNumberVisibility = #(lambda (n) (= (mo
On 14/01/14 06:30, Henning Hraban Ramm wrote:
Am 2014-01-14 um 03:09 schrieb Federico Bruni :
As you can see in this comment, PDF metadata are not documented:
https://code.google.com/p/lilypond/issues/detail?id=1463#c7
I think that this deserves an issue in the tracker.
Some interesting link:
On 12/01/14 17:50, pls wrote:
On 12.01.2014, at 18:07, David Kastrup wrote:
pls writes:
Hm, it's rather a conversion error of expressive marks in general in
combination with manual beaming (see file attached).
musicxml2ly places breath marks, dynamics, fermatas, etc. _within_
manual beam br
Patrice,
On 17/01/14 10:14, Patrice BRÉFORT wrote:
Hello,
Thank you very much for the great work you are doing with lilypond!
I noticed that when you create more than 9 footnotes in the same page with
the markup command named \auto-footnote, the delayed stencil used for
writing the number has
On 18/01/14 16:58, Jan Hajic, jr. wrote:
Hello,
the difference in processing of quotes and tags leads to unintuitive
behavior when quoting voices with tags. Specifically, this comes up in
exporting parts from a score: cues are for parts only and should not
be left in scores.
A minimal example i
Hello,
the difference in processing of quotes and tags leads to unintuitive
behavior when quoting voices with tags. Specifically, this comes up in
exporting parts from a score: cues are for parts only and should not
be left in scores.
A minimal example is:
---