Hi Urs,
Am Do., 25. Okt. 2018 um 17:49 Uhr schrieb Urs Liska :
>
> Hi Harm,
>
> thank you for this. From the *behaviour* this seems like what I need, but I
> have a few questions that may make it not really usable for my case.
>
>
> Am 24.10.2018 um 18:25 schrieb Thomas Morley:
>
> Am Di., 23.
Il giorno gio 25 ott 2018 alle ore 20:18 Thomas Morley
ha scritto:
> Davide wrote me a similiar mail, asking whether it's a bug in the
> docs. cc-ing him
I'm sorry, I meant to send my message to the list with you in cc, but
I hit the wrong button...
> "To set the staff size globally for all
Am Do., 25. Okt. 2018 um 14:30 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
> >>
> >> David Kastrup writes:
> >>
> >> > namely a bunch of Translator_creator s creating C++ engravers (maybe the
> >> > print expression should
Apologies if this is a known issue, but I think I've found a bug in the
regex/wildcard handling of edition engraver paths.
It seems that mixing editionMods with normal paths together with those formed
with wildcards and/or regular expressions causes the wildcard/regex editionMods
to break.
Am Do., 25. Okt. 2018 um 19:03 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi Thomas,
>
> > Yep, set-global-staff-size _must_ be set at top-level, outside of \book.
>
> That's good to know.
> The documentation got me going on using-it inside \book{}s.
>
Hi Thomas,
> Yep, set-global-staff-size _must_ be set at top-level, outside of \book.
That's good to know.
The documentation got me going on using-it inside \book{}s.
http://lilypond.org/doc/v2.19/Documentation/notation/setting-the-staff-size
> #(set-global-staff-size x)
> \book {}
>
Il giorno mer 24 ott 2018 alle ore 16:48 Davide Liessi
ha scritto:
> That instruction can be used only outside any variable, either in a
> \book block or outside any block (see
> http://lilypond.org/doc/v2.18/Documentation/notation/setting-the-staff-size).
This was apparently wrong: despite what
Hi Pierre-Luc,
Am Mi., 24. Okt. 2018 um 16:01 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Is this a bug?
>
> \version "2.21.0"
> %#(set-global-staff-size 4)
> \book {
> #(set-global-staff-size 4)
> \score {
> {\tempo 4=120 c4}
> \layout {}
> }
> }
>
> I'm trying to set the
Hi Harm,
thank you for this. From the *behaviour* this seems like what I need,
but I have a few questions that may make it not really usable for my case.
Am 24.10.2018 um 18:25 schrieb Thomas Morley:
Am Di., 23. Okt. 2018 um 08:28 Uhr schrieb Urs Liska :
Hi,
I want to use
Dear Davide,
thank you for the answer. that was exactly the problem… I just missed to get
myself the solution which is nevertheless very explicit in the manual. It is
easy for a newbie to get lost in the complications of Lilypond even in simple
matters.
And sorry for being a total newbie also
Thomas Morley writes:
> I'm tempted to create a patch along these lines.
> Though, there is no other usage of 'music-clone' in our code-base, afaict.
> It's far to useful to risk someone deletes it lateron regarding it as
> unused function.
Its functionality is rather similar to
Thomas Morley writes:
> Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
>>
>> David Kastrup writes:
>>
>> > namely a bunch of Translator_creator s creating C++ engravers (maybe the
>> > print expression should at least mention _which_ C++ engraver in order
>> > to make them look less
Am Mi., 24. Okt. 2018 um 16:00 Uhr schrieb David Kastrup :
>
> Thomas Morley writes:
>
> > Am Mi., 24. Okt. 2018 um 01:07 Uhr schrieb David Kastrup :
> >>
> >> Thomas Morley writes:
> >>
> >> > Am Di., 23. Okt. 2018 um 23:54 Uhr schrieb David Kastrup :
> >> >
> >> >> So you should figure out
Am Di., 9. Okt. 2018 um 01:24 Uhr schrieb David Kastrup :
>
> David Kastrup writes:
>
> > namely a bunch of Translator_creator s creating C++ engravers (maybe the
> > print expression should at least mention _which_ C++ engraver in order
> > to make them look less similar)
>
> which is actually
14 matches
Mail list logo
