I cannot reproduce the error (LilyPond 2.23.6 on Mac) - with or without setting tupletFullLengthNote = ##t
Thomas > Am 01.03.2022 um 12:38 schrieb Thomas Morley <thomasmorle...@gmail.com>: > > Am Di., 1. März 2022 um 11:58 Uhr schrieb Thomas Morley > <thomasmorle...@gmail.com>: >> >> Am Mo., 28. Feb. 2022 um 21:30 Uhr schrieb Paul Hodges <p...@cassland.org>: >>> >>> I've had this several times in my present project, each time with a clef in >>> the other Piano Staff - the triplet bracket, but not the triplet notes, is >>> forced not to share horizontal space with the clef. I can't see anything >>> I'm doing wrong which might prevent this being a bug. >>> >>> >>> I've managed for now with a hacky workaround (I reduce the length of the >>> item before the clef and put a tiny spacer rest after it), but obviously >>> I'd rather not do that in general. >>> >>> >>> Paul_______________________________________________ >>> bug-lilypond mailing list >>> bug-lilypond@gnu.org >>> https://lists.gnu.org/mailman/listinfo/bug-lilypond >> >> Hi Paul, >> >> this is >> https://gitlab.com/lilypond/lilypond/-/issues/610 >> Does adding >> \set tupletFullLengthNote = ##t >> help? >> If not, you may need to lengthen the TupletBracket manually, via >> shorten-pair. >> >> Cheers, >> Harm > > tupletFullLengthNote is not documented apart from: > http://lilypond.org/doc/v2.23/Documentation/snippets/rhythms#rhythms-modifying-tuplet-bracket-length > I'd vote for an entry in NR. > > Cheers, > Harm > > _______________________________________________ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
