Re: tagGroup question

2022-01-28 Thread David Kastrup
Simon Albrecht writes: > Thanks, David and Jean, for your replies. I have no intention to > reopen a can of worms here, and I didn’t remember that discussion > (IIRC, that was at a time when I more regularly kept up with all > LilyPond issues). > > Using \keepWithTag a \keepWithTag b \music is ve

Re: tagGroup question

2022-01-28 Thread Simon Albrecht
Thanks, David and Jean, for your replies. I have no intention to reopen a can of worms here, and I didn’t remember that discussion (IIRC, that was at a time when I more regularly kept up with all LilyPond issues). Using \keepWithTag a \keepWithTag b \music is very reasonable, especially consid

Re: tagGroup question

2022-01-28 Thread David Kastrup
David Kastrup writes: > Simon Albrecht writes: > >> Dear list, >> >> I have encountered some unexpected behaviour with tags and >> tagGroups. In the following example, I thought the two staffs should >> look the same, even without the \removeWithTag command, but they >> don’t: >> >>

Re: tagGroup question

2022-01-28 Thread David Kastrup
Simon Albrecht writes: > Dear list, > > I have encountered some unexpected behaviour with tags and > tagGroups. In the following example, I thought the two staffs should > look the same, even without the \removeWithTag command, but they > don’t: > > > \version "2.23.5" >

Re: tagGroup question

2022-01-28 Thread Jean Abou Samra
Le 28/01/2022 à 13:45, Simon Albrecht a écrit : Dear list, I have encountered some unexpected behaviour with tags and tagGroups. In the following example, I thought the two staffs should look the same, even without the \removeWithTag command, but they don’t: \version

tagGroup question

2022-01-28 Thread Simon Albrecht
Dear list, I have encountered some unexpected behaviour with tags and tagGroups. In the following example, I thought the two staffs should look the same, even without the \removeWithTag command, but they don’t: \version "2.23.5" % tested with 2.23.5 (guile2-build) and