Re: Learning Lilypond, comments invited - part 2

hi, On Fri, Jan 3, 2014 at 7:20 PM, David Kastrup wrote: > Noeck writes: > > With the promising caption "\set versus \override" and no content: > > > http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override > > Having spent quite a bit of time writing this section and makin

Re: Learning Lilypond, comments invited - part 2

- Original Message - From: "Noeck" To: "David Kastrup" ; Cc: Sent: Friday, January 03, 2014 6:30 PM Subject: Re: Learning Lilypond, comments invited - part 2 Hi David and Phil, I now realize that this is an issue with the translation. My browser redirects me

Re: Learning Lilypond, comments invited - part 2

Marc Hohl writes: > Am 03.01.2014 19:20, schrieb David Kastrup: >> Noeck writes: >> > Why do I see side by side two keywords for setting properties: \set > and \override. That is explained in the manual. >>> >>> With the promising caption "\set versus \override" and no content:

Re: Learning Lilypond, comments invited - part 2

Am 03.01.2014 19:20, schrieb David Kastrup: > Noeck writes: > Why do I see side by side two keywords for setting properties: \set and \override. >>> >>> That is explained in the manual. >> >> With the promising caption "\set versus \override" and no content: >> http://www.lilypond.org

Re: Learning Lilypond, comments invited - part 2

Hi David and Phil, I now realize that this is an issue with the translation. My browser redirects me automatically to the German version: http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override.de.html I now see that the English version of that page indeed has content that I

Re: Learning Lilypond, comments invited - part 2

Am 03.01.2014 19:20, schrieb David Kastrup: Noeck writes: Why do I see side by side two keywords for setting properties: \set and \override. That is explained in the manual. With the promising caption "\set versus \override" and no content: http://www.lilypond.org/doc/v2.18/Documentation/n

Re: Learning Lilypond, comments invited - part 2

Noeck writes: >>> Why do I see side by side two keywords for setting properties: \set >>> and \override. >> >> That is explained in the manual. > > With the promising caption "\set versus \override" and no content: > http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override H

Re: Learning Lilypond, comments invited - part 2

>> Why do I see side by side two keywords for setting properties: \set >> and \override. > > That is explained in the manual. With the promising caption "\set versus \override" and no content: http://www.lilypond.org/doc/v2.18/Documentation/notation/set-versus-override The preceding sections ar

Re: Learning Lilypond, comments invited - part 2

Colin Tennyson writes: > To use another analogy: our choir conductor sometimes asks in mild > exasparation: "Sing _something_ , never mind you're not sure. If you sing > the wrong note I can correct it, but if you don't sing at all I'm dead in > the water." > > So, in asking questions here on t

Re: Learning Lilypond, comments invited - part 2

ot; "\undo \hide" I see "consists" "\remove" I see "##t" and "##f" I wonder, how did the development of LilyPond end up with the syntax and keyword set that it now has? -- View this message in context: http://lilypond.1069038.n5.nabble.com/Lea

Re: Learning Lilypond, comments invited - part 2

Hi David, > No, they can also be added or removed in a context _modification_, as in > > \new Voice \with { \remove "..." \consists "..." } > { … } Thank you for the clarification/correction: engravers can be added or removed in a context definition or modification. Cheers, Kieren. __

Re: Learning Lilypond, comments invited - part 2

Kieren MacMillan writes: >> Can the property "forbid_line_break_engraver" also be accessed using >> a dot notation? > > Not that I’m aware of: engravers can only be added (\consists) or > removed (\remove) in a context definition. No, they can also be added or removed in a context _modification_

Re: Learning Lilypond, comments invited - part 2

Hi Colin, I will try to answer in a way that helps you. > the keyword \new instructs Lilypond to create a new instance of a class. You clearly come from a programming background, which will help you scale the Lilypond learning curve in some ways. However, don’t push that analogy too far, or yo

Re: Learning Lilypond, comments invited - part 2

Colin Tennyson writes: > I'm creating a new thread because the previous one has become somewhat > cluttered. > > My template is much better now, thank you for your suggestions. > > As emphasized by David Kastrup, the keyword \new instructs Lilypond to > create a new instance of a class. > \new S

Re: Learning Lilypond, comments invited - part 2

> Can the property "forbid_line_break_engraver" also be accessed using a dot > notation? I am not the only one ;) (David will understand what I want to say) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lil

Learning Lilypond, comments invited - part 2

et Score.barNumberVisibility = #(every-nth-bar-number-visible 5) \override Staff.InstrumentName.self-alignment-X = #RIGHT \context { \Voice \remove "Forbid_line_break_engraver" } %#(layout-set-staff-size 18) } %\midi { } } -- View this message in context: http