Re: GSoC update; Q's about final/draft modes, and triggering footnotes

> > For greater flexibility, would it be feasible to allow users to create and > name any number of their own modes (rather than having two "hard-coded")? > ​ > Just to put my two cents in, I ​had thought about that as well and almost suggested it in the OP. If a single project could employ

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

I'd appreciate any thoughts on the following syntax for implementing footnotes with annotations: \criticalRemark \with { message = "my annotation" } #'(1 . 2) "my footnote" Slur a4_\the-footnote-hook ( ... vs. \criticalRemark \with { message = "my annotation" footnote-offset = '(1 .

Re: space the width of key signature

On Sat, Jul 2, 2016 at 8:10 PM, David Nalesnik wrote: > > I think your method is sound. Besides the fact that it works, I > believe that items that respond to break-visibility are treated in a > similar manner. I could be wrong -- and please correct me if I am -- >

Re: Non-blank chord repeat

On Sat, Jul 2, 2016, 5:12 PM Thomas Morley wrote: > > > minus =\once \override ChordName.text = "-" > > Works beautifully, thanks, especially with a full em dash. > "Georgia on my Mind" is a rhythmic nightmare, and that helps tame it.

Re: space the width of key signature

On Sat, Jul 2, 2016 at 7:53 PM, David Nalesnik wrote: > On Sat, Jul 2, 2016 at 7:21 PM, David Nalesnik > wrote: >> On Sat, Jul 2, 2016 at 6:25 PM, Thomas Morley >> wrote: >> >>> >>> Thanks for your code, it will be

Re: space the width of key signature

On Sat, Jul 2, 2016 at 7:21 PM, David Nalesnik wrote: > On Sat, Jul 2, 2016 at 6:25 PM, Thomas Morley > wrote: > >> >> Thanks for your code, it will be a great simplification. >> Now I'd love to get rid of the engraver. All those

Re: space the width of key signature

On Sat, Jul 2, 2016 at 6:25 PM, Thomas Morley wrote: > > Thanks for your code, it will be a great simplification. > Now I'd love to get rid of the engraver. All those StanzaNumber-grobs, > first they are created and then most of them thrown away... > The exercise is to

Re: Non-blank chord repeat

2016-07-03 1:58 GMT+02:00 Thomas Morley : > 2016-07-03 0:03 GMT+02:00 Lee Daniel Crocker : >> I'm printing lead sheets with just chords and lyrics, and this makes the >> rhythm of the tune hard to see. What I'd like to do print chords at

Re: applyOutput Lyrics.LyricText not working?

Thomas Morley writes: > 2016-07-03 0:19 GMT+02:00 David Kastrup : >> >> Two possible ways to fix this: >> >> 1) add the Output_property_engraver on all possibly interesting >> Bottom(?) contexts >> 2) Move the Output_property_engraver to Score level only

Re: Non-blank chord repeat

2016-07-03 0:03 GMT+02:00 Lee Daniel Crocker : > I'm printing lead sheets with just chords and lyrics, and this makes the > rhythm of the tune hard to see. What I'd like to do print chords at regular > intervals, say every half note, and rather than having repeats

Re: space the width of key signature

2016-07-02 20:07 GMT+02:00 David Nalesnik : > Hi, > > On Sat, Jul 2, 2016 at 12:49 PM, David Nalesnik > wrote: >> Hi Harm, >> >> On Sat, Jul 2, 2016 at 10:43 AM, Thomas Morley >> wrote: >>> 2016-07-01 20:43 GMT+02:00

Re: applyOutput Lyrics.LyricText not working?

2016-07-03 0:19 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> Hi, >> >> consider the following two snippets: >> >> \version "2.19.44" >> >> \new ChordNames >> \chordmode { >>\applyOutput ChordNames.ChordName >> #(lambda (g ctx p) >>

Re: applyOutput Lyrics.LyricText not working?

Thomas Morley writes: > Hi, > > consider the following two snippets: > > \version "2.19.44" > > \new ChordNames > \chordmode { >\applyOutput ChordNames.ChordName > #(lambda (g ctx p) >(write-me "\ng" g) >(write-me "ctx" ctx) >(write-me

Non-blank chord repeat

I'm printing lead sheets with just chords and lyrics, and this makes the rhythm of the tune hard to see. What I'd like to do print chords at regular intervals, say every half note, and rather than having repeats suppressed, have them print "-". For example, "G - C - D C" for two beats of G, two

Re: Create custom Staff type

Thanks Paul, This helps a lot. But I'm very pleased with the solution Abraham Lee posted before. This snippet is very useful though for other things I want to try. -Dimitris -- View this message in context: http://lilypond.1069038.n5.nabble.com/Create-custom-Staff-type-tp192105p192114.html

applyOutput Lyrics.LyricText not working?

Hi, consider the following two snippets: \version "2.19.44" \new ChordNames \chordmode { \applyOutput ChordNames.ChordName #(lambda (g ctx p) (write-me "\ng" g) (write-me "ctx" ctx) (write-me "p" p) ) c } \new Lyrics \lyricmode { \applyOutput

Re: Create custom Staff type

On 07/02/2016 02:08 PM, David Kastrup wrote: \layout { \context { \Staff \name "HiddenStaff" \alias "Staff" \RemoveAllEmptyStaves } \inherit-acceptability HiddenStaff Staff } See also this snippet: http://lsr.di.unimi.it/LSR/Item?id=882 \inherit-acceptability

Re: Create custom Staff type

tisimst writes: > Dimitris, > > On Saturday, July 2, 2016, dtsmarin [via Lilypond] < > ml-node+s1069038n192107...@n5.nabble.com> wrote: > >> Thank you, but this is not what I'm looking for. >> I want a special type of "Engraver_group" like Staff, GrandStaff etc. >>

Re: space the width of key signature

Hi, On Sat, Jul 2, 2016 at 12:49 PM, David Nalesnik wrote: > Hi Harm, > > On Sat, Jul 2, 2016 at 10:43 AM, Thomas Morley > wrote: >> 2016-07-01 20:43 GMT+02:00 Br. Gabriel-Marie | SSPX : >>> Because stanza numbers only

Re: Create custom Staff type

Well this works for me, it just takes more time to configure in the file but I'm fine. Thanks again Abraham! -- View this message in context: http://lilypond.1069038.n5.nabble.com/Create-custom-Staff-type-tp192105p192110.html Sent from the User mailing list archive at Nabble.com.

Re: space the width of key signature

Hi Harm, On Sat, Jul 2, 2016 at 10:43 AM, Thomas Morley wrote: > 2016-07-01 20:43 GMT+02:00 Br. Gabriel-Marie | SSPX : >> Because stanza numbers only appear on the first line. Using instrumentName >> to label verse numbers provides automatic

Re: Create custom Staff type

Dimitris, On Saturday, July 2, 2016, dtsmarin [via Lilypond] < ml-node+s1069038n192107...@n5.nabble.com> wrote: > Thank you, but this is not what I'm looking for. > I want a special type of "Engraver_group" like Staff, GrandStaff etc. > e.g. > scoreAViolaPart = \new GrandStaff \with { \clef

Re: Create custom Staff type

Thank you, but this is not what I'm looking for. I want a special type of "Engraver_group" like Staff, GrandStaff etc. e.g. scoreAViolaPart = \new GrandStaff \with { \clef "alto" } << \set GrandStaff.systemStartDelimiter = #'SystemStartSquare \new Staff = "A" << \global \scoreAViolaAI \\

Re: Create custom Staff type

On Sat 02 Jul 2016 at 09:21:00 (-0700), dtsmarin wrote: > Hello, > I want to create a Staff type which will be used for hiding extra staves Ι > don't need. > Since I use every other available type of staves (Group,Grand,Piano etc.) > applying removeemptystaves will also affect other staves that I

Create custom Staff type

Hello, I want to create a Staff type which will be used for hiding extra staves Ι don't need. Since I use every other available type of staves (Group,Grand,Piano etc.) applying removeemptystaves will also affect other staves that I need. I tried to tweak the engraver-init file (found in

Re: space the width of key signature

2016-07-01 20:43 GMT+02:00 Br. Gabriel-Marie | SSPX : > Because stanza numbers only appear on the first line. Using instrumentName > to label verse numbers provides automatic numbering on every line. It > wasn't my idea, actually, credit for that goes to Thomas Morley a few

Re: space the width of key signature

This kind of problems clearly shows that it would be better to have a possibility of using actual stanza numbers. I created . Best, Simon On 01.07.2016 17:46, Br. Gabriel-Marie | SSPX wrote: There is this one song that is in c-minor and

Re: oddHeaderMarkup in score header

On 02.07.2016 03:30, Jaja wrote: I tried to typeset multiple scores without using bookpart or book block. So far, oddHeaderMarkup and evenHeaderMarkup cannot be applied to score header. The same problem happened with oddFooterMarkup and evenFooterMarkup. It would be very flexible and speed my

Re: Shorten a beam stem length

On 02.07.2016 04:22, Andrew Bernard wrote: Also, in your code, if you mean a length of 1, just use #1 for Scheme, not #’(1) as you had. Actually even the hash sign is unnecessary. Numbers mean the same in LilyPond syntax as in Scheme syntax (except for the special case of #.3 – that doesn’t

Re: tiny function

David Kastrup writes: > Thomas Morley writes: > >> Otoh, we can store things like \paper, \layout, \midi, \with and as >> off issue 4908 even \header in variables. >> But when called, the variable needs to be wrapped in a proper manner, >> sometimes not.

Re: tiny function

Thomas Morley writes: > Well, not really. As said before, my feelings were ambivalent. > > After reconsidering: > > It's more a possibility I sometimes use. Mostly because of lazyness in typing. > > Writing > \new Staff \with