Re: 2.23.81 new D.S. code

2022-11-16 Thread David Wright
On Wed 16 Nov 2022 at 06:21:41 (-0500), Kieren MacMillan wrote: > > >> What about creating all the parts for a score? I certainly > >> don't want to type all the common structure in each part. > > If you type the structure first, then as you use emacs, it's easy to > > copy and paste sufficient

Re: 2.23.81 new D.S. code

2022-11-16 Thread Jean Abou Samra
Le 16/11/2022 à 12:21, Kieren MacMillan a écrit : What about creating all the parts for a score? I certainly don't want to type all the common structure in each part. If you type the structure first, then as you use emacs, it's easy to copy and paste sufficient copies of it before you enter the

Re: 2.23.81 new D.S. code

2022-11-16 Thread Kieren MacMillan
Hi all, >> What about creating all the parts for a score? I certainly >> don't want to type all the common structure in each part. > If you type the structure first, then as you use emacs, it's easy to > copy and paste sufficient copies of it before you enter the notes. Okay… but yet another

Re: 2.23.81 new D.S. code

2022-11-15 Thread David Wright
On Tue 15 Nov 2022 at 14:41:28 (-0700), Paul Scott wrote: > On 11/15/22 1:57 PM, Jean Abou Samra wrote: > > Le 15/11/2022 à 21:50, Paul Scott a écrit : > > > What about creating all the parts for a score? I certainly > > > don't want to type all the common structure in each part. If you type the

Re: 2.23.81 new D.S. code

2022-11-15 Thread Kieren MacMillan
Hi Jean, > Clearer documentation would be a good first step, but my ultimate > wish would be a warning if this construct is used Yes, please! > because Hyrum's law That's the second apparently-reasonably-widely-known thing I learned about today! (The other was the Mendoza line.) Thanks for

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 23:03, Kieren MacMillan a écrit : It’s not for you to sweat about, though it will be nice to make things explicit in the documentation so nobody else builds up a 20-plus-year library of minefield-laden scores. Clearer documentation would be a good first step, but my

Re: 2.23.81 new D.S. code

2022-11-15 Thread Kieren MacMillan
Hi Jean (et al.), >> Interesting! It makes sense, of course… but I must admit that I have been >> using \repeat in my \global variable and NOT in my other note variables for >> my entire time using Lilypond, and [as far as I know] never ran into a >> problem. I really did think it was the

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 22:51, Kieren MacMillan a écrit : Hi all, On Nov 15, 2022, at 4:20 PM, Jean Abou Samra wrote: \repeat, on the other hand, is a command that does not stand alone but transforms a piece of music. It should be applied to all music that it is supposed to transform. Interesting!

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
On 11/15/22 2:51 PM, Kieren MacMillan wrote: Hi all, On Nov 15, 2022, at 4:20 PM, Jean Abou Samra wrote: \repeat, on the other hand, is a command that does not stand alone but transforms a piece of music. It should be applied to all music that it is supposed to transform. Interesting! It

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 22:46, Paul Scott a écrit : Did you see the documentation advising mismatched \repeat-s across staves? No, can you point me to it? See my previous message. The documentation does not do it apart from one example that is considered a documentation bug. OpenPGP_signature

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 22:41, Paul Scott a écrit : On 11/15/22 1:57 PM, Jean Abou Samra wrote: Le 15/11/2022 à 21:50, Paul Scott a écrit : What about creating all the parts for a score? I certainly don't want to type all the common structure in each part. It is really that troublesome? It's the

Re: 2.23.81 new D.S. code

2022-11-15 Thread Kieren MacMillan
Hi all, > On Nov 15, 2022, at 4:20 PM, Jean Abou Samra wrote: > \repeat, on the other hand, is a command that does not stand alone > but transforms a piece of music. It should be applied to all music > that it is supposed to transform. Interesting! It makes sense, of course… but I must admit

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
On 11/15/22 2:20 PM, Jean Abou Samra wrote: Le 15/11/2022 à 22:10, Paul Scott a écrit : On 11/15/22 13:57, Jean Abou Samra wrote: It is really that troublesome? Yes. It's the way it's intended to be used. ?? I learned much of what I do here and, of course, in the documentation I hope

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
On 11/15/22 1:57 PM, Jean Abou Samra wrote: Le 15/11/2022 à 21:50, Paul Scott a écrit : What about creating all the parts for a score? I certainly don't want to type all the common structure in each part. It is really that troublesome? It's the way it's intended to be used. Can you show

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 22:10, Paul Scott a écrit : On 11/15/22 13:57, Jean Abou Samra wrote: It is really that troublesome? Yes. It's the way it's intended to be used. ?? I learned much of what I do here and, of course, in the documentation I hope others will comment on this.  I'm sure I've seen

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
On 11/15/22 13:57, Jean Abou Samra wrote: Le 15/11/2022 à 21:50, Paul Scott a écrit : What about creating all the parts for a score? I certainly don't want to type all the common structure in each part. It is really that troublesome? Yes. It's the way it's intended to be used. ?? I

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 21:50, Paul Scott a écrit : What about creating all the parts for a score? I certainly don't want to type all the common structure in each part. It is really that troublesome? It's the way it's intended to be used. You will find that \section and \fine only affect their

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
On 11/15/22 1:42 PM, Jean Abou Samra wrote: By the way, I would strongly discourage your score structure: \version "2.23.81" timing = {   [\repeat segno stuff] } music = \fixed c' {   [without \repeat segno] } \score { \new Staff << \timing \music >> } LilyPond does not make efforts to

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
By the way, I would strongly discourage your score structure: \version "2.23.81" timing = {   [\repeat segno stuff] } music = \fixed c' {   [without \repeat segno] } \score { \new Staff << \timing \music >> } LilyPond does not make efforts to support differing repeat structures across

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
I forgot to send my reply to the list that I figured out 1. On 11/15/22 11:16 AM, Jean Abou Samra wrote: Le 15/11/2022 à 19:10, Paul Scott a écrit : I'm, trying to learn the new segno repeat structure. 1. Why do I get a second staff? This has nothing to do with segno repeats, you'll get

Re: 2.23.81 new D.S. code

2022-11-15 Thread Jean Abou Samra
Le 15/11/2022 à 19:10, Paul Scott a écrit : I'm, trying to learn the new segno repeat structure. 1. Why do I get a second staff? This has nothing to do with segno repeats, you'll get the same with \version "2.23.81" <<   { c }   { c' } >> The fix isto use \score { \new Staff << \timing

Re: 2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
I just answered 1. by adding \new Staff \new Voice in the score block. On 11/15/22 11:10 AM, Paul Scott wrote: I'm, trying to learn the new segno repeat structure. 1. Why do I get a second staff? 2. What does \volta #'() do? TIA for any help. Paul

2.23.81 new D.S. code

2022-11-15 Thread Paul Scott
I'm, trying to learn the new segno repeat structure. 1. Why do I get a second staff? 2. What does \volta #'() do? TIA for any help. Paul \version "2.23.81" timing = { \set Score.dalSegnoTextFormatter = #format-dal-segno-text-brief s1 \repeat segno 2 { s1 \alternative {