Hi Ken, I’d argue than in this example the Caesura is placed in a weird way, so we need to tell Lilypond to actually do it this way. That can be achieved by something as simple as
caesura = \tweak text \markup\musicglyph "scripts.caesura.straight" \tweak outside-staff-priority 100 \tweak space-alist #'((ambitus extra-space . 0) ; we could do '() if we can live with warnings (custos minimum-space . 0) (key-signature minimum-space . 0) (time-signature minimum-space . 0) (staff-bar minimum-space . 0) (clef minimum-space . 0) (cue-clef minimum-space . 0) (cue-end-clef minimum-space . 0) (first-note fixed-space . 0) (right-edge extra-space . 0)) \breathe { r4 e8 g b[ \caesura d' f' g'] } \addlyrics { just a step be -- yond the } Cheers, Valentin Am Sonntag, 1. Mai 2022, 18:19:26 CEST schrieb Kenneth Wolcott: > Hi Phil; > > Lilypond 2.22.2 Notation Reference explicitly states that. > > Thanks for your 2.23 documentation link as it does help, but by no > means looks like what I need (see attachment). > > Thanks, > Ken > > On Sun, May 1, 2022 at 2:27 AM Phil Holmes <m...@philholmes.net> wrote: > > AFAICS there is no requirement to use gregorian.ly to get a caesura. > > Why do you think there is? > > > > See > > https://lilypond.org/doc/v2.23/Documentation/notation/expressive-marks-as-> > > > curves#breath-marks> > > On 01/05/2022 06:38, Kenneth Wolcott wrote: > > > Hi; > > > > > > I see that the use of \caesura requires \include "gregorian.ly", > > > according to the Notation Reference. > > > > > > But doing this completely screws up all the default display Lilypond > > > code that I've been using all along. > > > > > > I'm trying to engrave "Somewhere Over the Rainbow", which definitely > > > does not belong in the Gregorian time period or style. > > > > > > Yet this piece of music does have two instances of a caesura. > > > > > > Is there a solution to this conundrum? Can I safely cherry pick the > > > definition of the caesura out of the "gregorian.ly" file? > > > > > > Thanks, > > > Ken Wolcott
signature.asc
Description: This is a digitally signed message part.