Re: Weirdness with \set associatedVoice

2018-12-17 Thread Michael Gerdau
Hi David, > > Is my understanding of what \set associatedVoice does flawed or is this a > > bug? > > Without exactly working through the interaction with staff as opposed > to voice, you should know that "\one one" has never worked: the > set associated voice command has to be placed one syllabl

Re:Combine these segments for same score

2018-12-17 Thread Flaming Hakama by Elaine
> > -- Forwarded message -- > From: Reggie > To: lilypond-user@gnu.org > Date: Sun, 16 Dec 2018 13:17:19 -0700 (MST) > Subject: Re: Combine these segments for same score > David Wright wrote > > On Sun 16 Dec 2018 at 11:05:05 (-0700), Reggie wrote: > >> Urs Liska-3 wrote > >> > one

Re: Weirdness with \set associatedVoice

2018-12-17 Thread Phil Holmes
- Original Message - From: "Michael Gerdau" To: ; "David Wright" Sent: Monday, December 17, 2018 8:46 AM Subject: Re: Weirdness with \set associatedVoice Hi David, > Is my understanding of what \set associatedVoice does flawed or is this > a bug? Without exactly working through t

Re: Weirdness with \set associatedVoice

2018-12-17 Thread Michael Gerdau
> See https://sourceforge.net/p/testlilyissues/issues/1354/ Thank you, at least that explains it. But it remains a PITA 😀 Kind regards, Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: feathered beam calculations

2018-12-17 Thread N. Andrew Walsh
Hi Reggie, well, my "solution" was that the client changed his mind and didn't want a ritardando there, so I did away with them. But no, I've never found a good way to calculate feathered beams (nor how to space them properly to match their changing duration values). This seems like something Lil

Re: feathered beam calculations

2018-12-17 Thread Reggie
Vaughan McAlley wrote > On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh < > n.andrew.walsh@ > > > wrote: > >> Hi List, >> >> I'm trying to use the \featherDurations command on a brief passage: >> >> \relative c' { >> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\) >> \override Beam

Re: feathered beam calculations

2018-12-17 Thread Reggie
Vaughan McAlley wrote > On Fri, 15 Dec 2017 at 19:34, N. Andrew Walsh < > n.andrew.walsh@ > > > wrote: > >> Hi List, >> >> I'm trying to use the \featherDurations command on a brief passage: >> >> \relative c' { >> a,,^\markup { \italic "subito meno mosso" }\( b cis dis eis8\) >> \override Beam

Formatting part of a header property

2018-12-17 Thread Br. Samuel Springuel
I'm making use of a custom header (with custom fields) and have come across a situation in which I need to apply custom formatting (italics) to a piece of the field (just a handful of words in the middle). Given that the header fields are normally simple strings, is there a way to format part

Re: Formatting part of a header property

2018-12-17 Thread David Kastrup
"Br. Samuel Springuel" writes: > I'm making use of a custom header (with custom fields) and have come > across a situation in which I need to apply custom formatting > (italics) to a piece of the field (just a handful of words in the > middle). Given that the header fields are normally simple st

Re: Formatting part of a header property

2018-12-17 Thread Br. Samuel Springuel
On 2018-12-17 12:08 PM, David Kastrup wrote: Uh, anything wrong with the obvious custom = \markup { PRAELUDIUM I \italic { italicized text } Back to normal } ? It works in the MWE I posted, but not in my original use case (the contents of the field disappear entirely. After some furth

Re: Formatting part of a header property

2018-12-17 Thread Thomas Morley
Am Mo., 17. Dez. 2018 um 19:21 Uhr schrieb Br. Samuel Springuel : > > On 2018-12-17 12:08 PM, David Kastrup wrote: > > Uh, anything wrong with the obvious > > > >custom = \markup { PRAELUDIUM I \italic { italicized text } Back to > > normal } > > > > ? > It works in the MWE I posted, but n

Re: Formatting part of a header property

2018-12-17 Thread David Kastrup
Thomas Morley writes: > Am Mo., 17. Dez. 2018 um 19:21 Uhr schrieb Br. Samuel Springuel > : >> >> On 2018-12-17 12:08 PM, David Kastrup wrote: >> > Uh, anything wrong with the obvious >> > >> >custom = \markup { PRAELUDIUM I \italic { italicized text } >> > Back to normal } >> > >> > ? >>

Re: Formatting part of a header property

2018-12-17 Thread David Kastrup
Thomas Morley writes: > Am Mo., 17. Dez. 2018 um 21:20 Uhr schrieb David Kastrup : >> >> Thomas Morley writes: > >> > The idea: >> > >> > #(define-markup-command (wordwrap-field layout props symbol) >> > (symbol?) > [doc-string dropped] >> > (let* ((m (chain-assoc-get symbol props))) >> >

Re: Formatting part of a header property

2018-12-17 Thread Thomas Morley
Am Mo., 17. Dez. 2018 um 21:20 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > The idea: > > > > #(define-markup-command (wordwrap-field layout props symbol) > > (symbol?) [doc-string dropped] > > (let* ((m (chain-assoc-get symbol props))) > > (cond ((string? m) > >(

Re: feathered beam calculations

2018-12-17 Thread Thomas Morley
Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie : > How do you change the amount of "beams" you feather when > the amount of notes is example 3. You need to just forget it? 3 beams are > not possible? > > \relative d { > \clef bass > \time 4/4 > d2 e4 > \override Beam.grow-direction = #

Re: feathered beam calculations

2018-12-17 Thread Reggie
Thomas Morley-2 wrote > Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie < > reegistoop@ > >: > >> How do you change the amount of "beams" you feather when >> the amount of notes is example 3. You need to just forget it? 3 beams >> are >> not possible? >> >> \relative d { >> \clef bass >>

Re: Formatting part of a header property

2018-12-17 Thread Br. Samuel Springuel
Thanks Harm. The code may not be fully tested, but it does seem to do the job for me. There was one issue I ran into. I have a `\wordwrapright-field` and `\wordwrapcenter-field` which I make use of in this project and I had to load your code before I defined those commands (if done in revers

Re: feathered beam calculations

2018-12-17 Thread Thomas Morley
Am Mo., 17. Dez. 2018 um 22:13 Uhr schrieb Reggie : > > Thomas Morley-2 wrote > > Am Mo., 17. Dez. 2018 um 14:52 Uhr schrieb Reggie < > > Scale durations: > > > > \relative d { > > \clef bass > > \override Beam.grow-direction = #RIGHT > > \featherDurations #(ly:make-moment 3/4) > > c16*4

Re: Formatting part of a header property

2018-12-17 Thread Thomas Morley
Am Mo., 17. Dez. 2018 um 21:36 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Mo., 17. Dez. 2018 um 21:20 Uhr schrieb David Kastrup : > >> > >> Thomas Morley writes: > > > >> > The idea: > >> > > >> > #(define-markup-command (wordwrap-field layout props symbol) > >> > (symbol?)

Re: Formatting part of a header property

2018-12-17 Thread David Kastrup
Thomas Morley writes: > Am Mo., 17. Dez. 2018 um 21:36 Uhr schrieb David Kastrup : >> >> Thomas Morley writes: >> >> > Though, every string is a simple markup, yes, thus it's checked first. >> > Why do you think it's icky? >> >> Because a string is formatted/treated _differently_ from a markup.

Merge_rests_engraver broken?

2018-12-17 Thread Brent Annable
Hi all, Is the Merge_rests_engraver broken? I just copied and pasted the example from the Lilypond manual into Frescobaldi (Lilypond version 2.19.65), and the rests did not merge like they do on the relevant page of the manual

RE: Merge_rests_engraver broken?

2018-12-17 Thread Mark Stephen Mrotek
Brent, Copied, pasted, ran it. Mark From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Brent Annable Sent: Monday, December 17, 2018 6:39 PM To: lilypond-user Subject: Merge_rests_engraver broken? Hi all, Is the Merge_rests_engraver b