On 29/09/14 20:18, Federico Bruni wrote:
> 2014-09-29 21:12 GMT+02:00 Abraham Lee :
>
>> Put the overrides in a \layout block, like:
>>
>> \layout {
>> \override TabStaff.Stemstencil = ##f
>> }
>>
>> This won't create a new context, but it will apply it when you create one.
>>
>
> It's also a w
2014-09-30 0:41 GMT+02:00 Peter Crighton :
> 2014-09-29 21:18 GMT+02:00 Federico Bruni :
>
>> 2014-09-29 21:12 GMT+02:00 Abraham Lee :
>>
>>> Put the overrides in a \layout block, like:
>>>
>>> \layout {
>>> \override TabStaff.Stemstencil = ##f
>>> }
>>>
>>> This won't create a new context, but
2014-09-30 4:55 GMT+02:00 Abraham Lee :
> Sorry, I forgot to add "()" after "(parser location)". So, it should be
> like this:
>
> improvisationOn = #(define-scheme-function (parser locations) ()
> #{
> (Insert overrides)
> #}
> )
>
> However, it looks like you are doing the right thing even wit
Sorry, I forgot to add "()" after "(parser location)". So, it should be like
this:
improvisationOn = #(define-scheme-function (parser locations) ()
#{
(Insert overrides)
#}
)
However, it looks like you are doing the right thing even without this, since
you are following the same syntax as the
2014-09-30 0:49 GMT+02:00 Abraham Lee :
> If it's something you need to be able to call on-demand, then put it in a
> scheme function (you might need another one to turn it off):
>
> improvisationOn = #(define-scheme-function (parser location)
> #{
> (insert overrides here)
> #})
>
Thanks
On Mon, Sep 29, 2014 at 4:41 PM, Peter Crighton
wrote:
2014-09-29 21:18 GMT+02:00 Federico Bruni :
2014-09-29 21:12 GMT+02:00 Abraham Lee :
Put the overrides in a \layout block, like:
\layout {
\override TabStaff.Stemstencil = ##f
}
This won't create a new context, but it will apply it whe
2014-09-29 21:18 GMT+02:00 Federico Bruni :
> 2014-09-29 21:12 GMT+02:00 Abraham Lee :
>
>> Put the overrides in a \layout block, like:
>>
>> \layout {
>> \override TabStaff.Stemstencil = ##f
>> }
>>
>> This won't create a new context, but it will apply it when you create one.
>>
>
> It's also a
2014-09-29 21:12 GMT+02:00 Abraham Lee :
> Put the overrides in a \layout block, like:
>
> \layout {
> \override TabStaff.Stemstencil = ##f
> }
>
> This won't create a new context, but it will apply it when you create one.
>
It's also a way to keep music and style separated.
Bug Squad, what ab
On Mon, Sep 29, 2014 at 1:05 PM, Peter Crighton
wrote:
I see, thanks.
I have several files I include in every project, in one of which I
make some overrides to TabStaff.
How can I avoid this problem in scores I’m not using any TabStaffs
in, other than removing the Clef_engraver from TabSt
2014-09-29 20:57 GMT+02:00 Federico Bruni :
> 2014-09-29 20:50 GMT+02:00 Peter Crighton :
>
>> I’m pretty sure this is not expected output, is it? (See attached image.)
>>
>> \version "2.19.13"
>>
>> <<
>>
>> \override TabStaff.Stem.stencil = ##f
>>
>> c'1
>>
>> >>
>>
>>
>> This seems to occur
2014-09-29 20:50 GMT+02:00 Peter Crighton :
> I’m pretty sure this is not expected output, is it? (See attached image.)
>
> \version "2.19.13"
>
> <<
>
> \override TabStaff.Stem.stencil = ##f
>
> c'1
>
> >>
>
>
> This seems to occur with every kind of TabStaff override.
>
http://www.lilypond.
11 matches
Mail list logo
