Skip to content

Latest commit

 

History

History
49 lines (43 loc) · 4.84 KB

TODO_lilypond_updates.md

File metadata and controls

49 lines (43 loc) · 4.84 KB
Raw

LilyPond Update To-Do List

List of relevant LilyPond updates that might simplify / modify / otherwise affect functionality added in this package.

General notes

v2.22

  • Swing and irregular rhythmic patterns may now be applied to music expressions made of regular durations, which may be used to render inequal rhythmic interpretation in MIDI.
    • Consider providing an example for this?
    • How does this work with Festival output?
  • As announced in version 2.17.3 nearly eight years ago, the 'relative-includes option is now enabled by default; included files that contain an \include command of their own must account for their own path rather than the main file’s directory. That behavior may however be switched off by setting 'relative-includes to #f, either as a command line option or using ly:set-option in source files.
    • Does this break anything?

v2.24

  • The new \section command inserts a double bar line that interacts gracefully with repeat bar lines. A passage can be named with the new \sectionLabel command.
    • This should replace the \newSection functionality completely
  • The \rhythm markup command has been added. It is a simple way to enter rhythms mixed with text, such as in “swing” indications.
    • Consider adding an example of this?
  • \bar "" is no longer necessary to print the first bar number. It now suffices to set barNumberVisibility to all-bar-numbers-visible, or one of the other visibility settings where the first bar number is visible.
    • I think this should suffice to render any fixes in the current version unnecessary
  • Due to changes in the internals of \bar, it is no longer supported to use it before creating lower contexts with \new. Such uses will now create an extra staff. This is similar to what happens with commands such as \override Staff… (see An extra staff appears).
    • I do not believe this affects this package, but should verify
  • The comma glyph shape, as used in the \breathe command, has been changed to a more common form.
    • I do not believe this affects this package, but should verify
  • The new context property breathMarkType selects the mark that \breathe produces from several predefined types.
    • Does this affect the definition of caesura?
  • New commands \textMark and \textEndMark are available to add an arbitrary piece of text between notes, called a text mark. These commands improve over the previously existing syntax with the \mark command called as \mark markup (i.e., \mark "…" or \mark \markup …).
    • Should improve text markup
    • Consider adding an example of this?
  • \smallCaps now works on any markup, not just on a bare string.
    • This may have impacts; verify
  • The syntax for conditions in markups was made more flexible and user-friendly. It uses the new markup commands \if and \unless. Here are example replacements:
    • This should have impacts on layout definitions
  • With the new markup list command string-lines it is now possible to split a string at a given character. The default is to split at line break. Surrounding white space gets dropped. The resulting list of markups may be further formatted. This is a very convenient way of entering additional stanzas for songs.
    • Does this make performance notes easier to specify?
  • Text replacements can now replace strings with any markup, not just with a string.
    • This should not have impacts, but could take a look
  • The new show-horizontal-skylines and show-vertical-skylines properties allow to display an object’s skylines. This is more flexible than the already existing debug-skylines option because it works for all grobs. While primarily meant for debugging LilyPond, this can be useful when trying to understand spacing decisions or overriding stencils in Scheme.
    • Relevant to debug settings
  • The new command \vshape is like \shape, but also shows the control points and polygon for easier tweaking.
    • Could this allow for easier melody transitions, in any way? Unclear.
  • SCHEME TRANSLATOR IMPROVEMENTS
    • Would need to come back to understand more
  • The format function now requires a boolean or port as the first argument. This argument was optional in Guile 1.8. In order to make the function return the formatted output as a string, like format does without this argument in Guile 1.8, pass #f for this argument, i.e., (format #f "string" arguments …) instead of (format "string" arguments …).
    • Hopefully does not affect this package