On 3/26/21, 5:41 PM, "lilypond-user on behalf of Valentin Petzel"
<lilypond-user-bounces+carl.d.sorensen=gmail....@gnu.org on behalf of
valen...@petzel.at> wrote:
Your points about beaming and grouping are reasonable, but the idea is not
replacing tuplet with such a notation, but making such notation easier. And
there are many cases where the default grouping by beat structure is pretty
much what you want. In the worst case one can simply group the notes
manually,
which is still much faster than doing lots of different tuplets and hiding
the
Brackets (if you do a piece that frequently changes between division 2 and
division 3 this takes a stupid amount of time!)
You could easily write your own music function to write in division 3.
\inThree {c8 c c}
Or \"in3"{c8 c c}
Or \in³{c8 c c}
Your function could do whatever you would like to do about hiding brackets or
anything else you wanted to do.
And it wouldn't require rewriting LilyPond's parser. Or hardwire
non-conventional notation into LilyPond's core.
Carl
