Hello Simon,
Thanks for the clarification!
JM
> Le 23 sept. 2016 à 23:51, Simon Albrecht a écrit :
>
> On 23.09.2016 17:43, Menu Jacques wrote:
>> Hello folks,
>>
>> musicxml2ly as delivered with LP 2.19.35 produces score specifications such
>> as:
>>
>> % The score definition
>> \score {
>
On 23.09.2016 17:43, Menu Jacques wrote:
Hello folks,
musicxml2ly as delivered with LP 2.19.35 produces score specifications such as:
% The score definition
\score {
<<
\new Staff <<
\context Staff <<
\context Voice = "PartPOneVoiceOne" { \PartPOneVoi
Hello folks,
musicxml2ly as delivered with LP 2.19.35 produces scores specifications such as:
% The score definition
\score {
<<
\new Staff <<
\context Staff <<
\context Voice = "PartPOneVoiceOne" { \PartPOneVoiceOne }
\new Lyrics \lyricsto
It depends. It can be easier to read when they are all below the staff.
On Tue, Jan 7, 2014 at 12:12 PM, Noeck wrote:
> > Figured bass can be displayed using the FiguredBass context, or in most
> > staff contexts.
>
> Hi Simon,
>
> thanks for the explanation!
>
> This means bass figures should
> Figured bass can be displayed using the FiguredBass context, or in most
> staff contexts.
Hi Simon,
thanks for the explanation!
This means bass figures should be associated to the staff this way to
enhance the flexibility? I take this as such.
Cheers,
Joram
_
hi,
On Mon, Jan 6, 2014 at 6:42 PM, Noeck wrote:
> Hi,
>
> when looking at this snippet: http://lsr.dsi.unimi.it/LSR/Snippet?id=292
> I have the following question:
>
> Why is \context Staff allowed here? How can I fill bass figures in a Staff?
>
> I thought I need a \new FiguredBass context fo
Hi,
when looking at this snippet: http://lsr.dsi.unimi.it/LSR/Snippet?id=292
I have the following question:
Why is \context Staff allowed here? How can I fill bass figures in a Staff?
I thought I need a \new FiguredBass context for the \continuo. This
works indeed (%2) but I loose the ability to
Keith OHara writes:
> LilyPond's grammar, however, is complex due to history and its complex
> job. It is twice the length of that for C or Pascal, and growing. I
> have tried to use the printed grammar to understand LilyPond, but
> never succeeded.
Well, in the last two years, many things hav
Trevor Daniels treda.co.uk> writes:
> Joram Berger wrote Thursday, December 06, 2012 10:56 PM
>
> > Am 06.12.2012 23:51, schrieb Trevor Daniels:
> >>
> >> Have a look. You can see the LilyPond grammar in Appendix C
> >> of the Notation Reference.
> >>
> >> http://www.lilypond.org/doc/v2.17/Do
Am 06.12.2012 23:51, schrieb Trevor Daniels:
>
> Noeck wrote
>
>> It still seems to me like there might be a possiblity to simplify the
>> ly-syntax. Let me make a little comparison:
>>
>> I do not know the parser, but wouldn't it be possible to recognize
>> whether a named context already exis
ts
>> start with a keyword starting with backslash for that reason, or with
>> special characters.
> I rather meant the necessity of \new and \context, so
> \Staff = "var" { a4 }
> \Staff = "var" …or even (?) \var …
>
>>> I think it i
ackslash for that reason, or with
> special characters.
I rather meant the necessity of \new and \context, so
\Staff = "var" { a4 }
\Staff = "var" …or even (?) \var …
>> I think it is always better to make the usage of the software easy,
>> than having to e
Noeck, you wrote Thursday, December 06, 2012 11:58 PM
> Am 07.12.2012 00:24, schrieb Trevor Daniels:
>>
>> It's the LilyPond grammar as extracted from the input to Bison (somewhat
>> simplified). Bison generates the parser which then implements this
>> grammar.
>> You need to understand th
Noeck writes:
> I do not know the parser, but wouldn't it be possible to recognize
> whether a named context already exists and use that one and if not
> create a new one. That those lines could shrink to:
> Staff "var" { a4 }
> Staff "var" …or even (?) \var …
Staff and "var" are valid lyr
Am 07.12.2012 00:24, schrieb Trevor Daniels:
>
> Joram Berger wrote Thursday, December 06, 2012 10:56 PM
>
>> Am 06.12.2012 23:51, schrieb Trevor Daniels:
>>>
>>> Noeck wrote
>>>
It still seems to me like there might be a possiblity to simplify the
ly-syntax. Let me make a little compar
Joram Berger wrote Thursday, December 06, 2012 10:56 PM
> Am 06.12.2012 23:51, schrieb Trevor Daniels:
>>
>> Noeck wrote
>>
>>> It still seems to me like there might be a possiblity to simplify the
>>> ly-syntax. Let me make a little comparison:
>>>
>>> I do not know the parser, but wouldn't it
Noeck wrote
> It still seems to me like there might be a possiblity to simplify the
> ly-syntax. Let me make a little comparison:
>
> I do not know the parser, but wouldn't it be possible to recognize
> whether a named context already exists and use that one and if not
> create a new one.
Have
Am 05.12.2012 09:39, schrieb Trevor Daniels:
>
> Noeck, you wrote Tuesday, December 04, 2012 8:43 PM
>
>> what is the difference between \new and \context?
>
> Very little. In most situations they can be used interchangeably.
>
> One difference is that \context St
"Trevor Daniels" writes:
> Noeck, you wrote Tuesday, December 04, 2012 8:43 PM
>
>> Where would I need \context?
>> There is an example:
>> <<
>> \new Staff \context Voice = "A" \music
>> \context Voice = "A" \arts
>> >>
>> But I could write \new Staff << \music \\ \arts >>, couldn't I?
>
> Yes
Noeck, you wrote Tuesday, December 04, 2012 8:43 PM
> what is the difference between \new and \context?
Very little. In most situations they can be used interchangeably.
One difference is that \context Staff = "A" will search for a previously
defined Staff with the same name
Hi,
what is the difference between \new and \context?
I have read 5.1.2 Creating contexts, but I don't understand it yet.
It talks about 3 commands for a context:
\new type music expression
\context type = id music
\context type music
Why is \new type = id music not listed with an
21 matches
Mail list logo