> oo = #(define-music-function (parser location prop value)
>(symbol-list? scheme?)
> #{ \once \override #prop = #value #})
>
> should likely work fine in 2.18.
Thanks! Aaron provided this version
oo = #(define-music-function (parser location prop value)
(list?
> I side step the whole thing by having dynamic expanable macros in
> the text editor.
But this gives overlong lines, which I want to avoid for snippets
taken from the LSR and being part of the NR.
> And why use 2.18?
Because right now LSR is still using this version.
Werner
I side step the whole thing by having dynamic expanable macros in the
text editor.
And why use 2.18?
Andrew
On 28/08/2020 6:10 am, Werner LEMBERG wrote:
Folks,
I wonder whether there is a possibility to have a working equivalent
to
oo = \once\override
so that I can say
\oo
Werner LEMBERG writes:
>>> I wonder whether there is a possibility to have a working equivalent
>>> to
>>>
>>> oo = \once\override
>>>
>>> so that I can say
>>>
>>> \oo foo.bar = #'baz .
>>
>> The best you can aim for is
>>
>> \oo foo.bar #'baz
>
> This would be just fine. The thing is
Am Mi., 26. Aug. 2020 um 20:42 Uhr schrieb Claire Meyer
:
>
> Hi,
>
> I'm trying to reproduce a piano score that has a lot of cross-staff notes,
> some of them colliding. There are 3 voices :
> - one for the right hand on the upper staff,
> - one for the left hand on the lower staff,
> - and for
> Like this, I would imagine:
>
>
> \version "2.18.2"
>
> oo =
> #(define-music-function
> (parser location grob-path value)
> (list? scheme?)
> #{ \once \override $grob-path = #value #})
Great, thanks!
Werner
On 2020-08-27 1:27 pm, David Kastrup wrote:
Werner LEMBERG writes:
Folks,
I wonder whether there is a possibility to have a working equivalent
to
oo = \once\override
so that I can say
\oo foo.bar = #'baz .
It should work with LilyPond 2.18, BTW.
A quick search in the internet
Am Do., 27. Aug. 2020 um 20:53 Uhr schrieb Mark Stephen Mrotek
:
>
> Hello,
>
>
>
> In the attached snippet the stems should connect.
>
> I have been following
>
> http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems
>
> yet I must be missing
>> I wonder whether there is a possibility to have a working equivalent
>> to
>>
>> oo = \once\override
>>
>> so that I can say
>>
>> \oo foo.bar = #'baz .
>
> The best you can aim for is
>
> \oo foo.bar #'baz
This would be just fine. The thing is to replace `\once\override`
with
Werner LEMBERG writes:
> Folks,
>
>
> I wonder whether there is a possibility to have a working equivalent
> to
>
> oo = \once\override
>
> so that I can say
>
> \oo foo.bar = #'baz .
>
> It should work with LilyPond 2.18, BTW.
>
> A quick search in the internet didn't bring something
Folks,
I wonder whether there is a possibility to have a working equivalent
to
oo = \once\override
so that I can say
\oo foo.bar = #'baz .
It should work with LilyPond 2.18, BTW.
A quick search in the internet didn't bring something relevant. Help
would be much appreciated.
Hello,
In the attached snippet the stems should connect.
I have been following
http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-key
boards#cross_002dstaff-stems
yet I must be missing something.
Mark
\version "2.19.49"
\score {
\layout{
indent = #0
On Wed, 2020-08-26 at 21:34 +0100, David Sumbler wrote:
> On Wed, 2020-08-26 at 19:51 +0200, Toine Schreurs wrote:
> > > I want each line to go to the centre of the invisible notehead,
> > > so
> > > that
> > > I get a continuous line. Of course, the first and last lines
> > > only
> > > want
>
Claire,
Shall try somethings this morning and get back to you.
Mark
From: Claire Meyer [mailto:claire.meyer.bourhis.lilyp...@gmail.com]
Sent: Thursday, August 27, 2020 9:40 AM
To: Mark Stephen Mrotek
Cc: Lilypond-User Mailing List
Subject: Re: Problem with cross-staff colliding
Mark,
Thank you very much. Well, yes, the cross-staff is necessary, so I've been
trying to follow the examples in the documentation you sent, but either I'm
missing something, either they just don't apply to my case, or it's what
I've already used. The \change Staff and \autochange commands only
Hello all!
I'm hoping to [finally!] wrestle my large and currently unwieldy collection of
stylesheets into public-worthy form. This effort is really the perfect time to
[finally!] implement a real stylesheet system in OpenLilyLib, so that the
concept of stylesheets can easily be adopted, used,
On Tue 25 Aug 2020 at 18:30:47 (+0200), Claire Meyer wrote:
> @Gilles Sadowski :
> Thanks, it works! Interestingly, though, I had to iterate down to 16,
> because 19, 18, 17 *and 20* produce bigger outputs than default. They all
> produce 5 pages. And yet, *20 is the default*. If anyone can
This might also be useful depending on what you are after:
http://lsr.di.unimi.it/LSR/Item?id=654
Le jeu. 27 août 2020 à 11:34, Timothy Lanfear a écrit :
> Provided you use a recent version of Lilypond, e.g. 2.20.0, the pitch is
> carried forward from the previous note and you can write c4. 8
Provided you use a recent version of Lilypond, e.g. 2.20.0, the pitch is
carried forward from the previous note and you can write c4. 8 4.
From: lilypond-user On
Behalf Of Alasdair McAndrew
Sent: 27 August 2020 09:49
To: lilypond-user Mailinglist
Subject: Question about abbreviations
Hi.
2020-08-27 10:48 UTC+02:00, Alasdair McAndrew :
> Hello,
>
> I don't know if this is possible in Lilypond, so I'm asking the experts...
> In a bar of 3/4 time I might have, say: c4. c8 c4 - a very standard
> rhythm. I remember once that in a score-writing system I used years ago,
> this
Hello,
I don't know if this is possible in Lilypond, so I'm asking the experts...
In a bar of 3/4 time I might have, say: c4. c8 c4 - a very standard
rhythm. I remember once that in a score-writing system I used years ago,
this could be abbreviated as c>c c. I know that < > are used in Lilypond
21 matches
Mail list logo
