|
From: | Auto mailings of changes to Lily Issues via Testlilyissues-auto |
Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5486 add fermata markup commands |
Date: | Sun, 28 Apr 2019 08:15:03 -0000 |
Now that [#5511] is solved I’m not sure we need markup commands for all fermata types. Do we? If someone wants to write \markup \column { "ad lib." \longfermata }
couldn’t they just use \markup \column { "ad lib." \musicglyph #"scripts.longfermata" }
? You wouldn’t have automatic directions then. But to me it seems as if adding six new markup commands or a single fermata markup command that can do fermatas but not other scripts much effort for little benefit.
[issues:#5486] add fermata markup commands
Status: Started
Created: Thu Feb 28, 2019 09:07 AM UTC by Malte Meyn
Last Updated: Fri Apr 19, 2019 11:55 AM UTC
Owner: Malte Meyn
add fermata markup commands
Like the markup command \fermata and \fermataMarkup there are now:
\shortfermata, \longfermata, \verylongfermata
\shortfermataMarkup, \longfermataMarkup, \verylongfermataMarkup
contains also: add fermata markup commands to docs
http://codereview.appspot.com/344160043
Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Prev in Thread] | Current Thread | [Next in Thread] |