Skip to content

lilypond-book: Some fixes and improvements

Werner Lemberg requested to merge dev/wl/lilypond-book into master

  • lilypond-book: Improve documentation of --filter option

    • Replace a confusing usage example for --filter in lilypond-book's help output with something better.

    • Don't use 'BOOK' but 'FILE' in lilypond-book's help output.

    • In the documentation, remove an obsolete comment and clarify what --filter actually does.

  • lilypond-book: Fix --filter option for Texinfo format

    • In the regexes for snippet parsing, don't include trailing whitespace in the 'code' group. This harmonizes the handling of inline and block 'lilypond' commands.

    • Fix --filter for Texinfo documents; it didn't work with inline snippets.

  • lilypond-book: Don't show internal option --highlight in help output

  • lilypond-book: Handle @verb and @verbatim in Texinfo files

    It is now possible to have stuff like

    @verb{|@lilypond[fragment]{c4}|}

    and

    @verbatim
@lilypond
c4
@end lilypond
@end verbatim

    in a similar way as in LaTeX or HTML input.

    Note that @verb and @verbatim were introduced in texinfo 4.1, which was released in 2002. The previous, no longer working code apparently predated this since it used @code and @example.

  • lilypond-book: Fix HTML input handling

    • Remove verbatim regexes for HTML input.

      Within a <pre> block, other HTML tags are not ignored. Consequently, <lilypond> and friends make sense within <pre> only if they are actually interpreted.

    • Handle HTML comments correctly.

      Bug was present since the beginning of HTML support (in 2002).

  • lilypond-book: Update and add tests for ignoring verbatim input

  • lilypond-book: Update and add tests for ignoring comments

Edited by Werner Lemberg

Merge request reports