[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lilypond-book] @format environments

From: Michael Käppler
Subject: Re: [lilypond-book] @format environments
Date: Fri, 10 Jul 2020 13:45:59 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

Am 09.07.2020 um 18:09 schrieb Trevor:
Michael Käppler, you wrote 09/07/2020 12:45:28

What strikes me the most is that 'addversion' is used only three times
throughout the
whole documentation, and these three occurrences are all in the LM,

What is the reason that the version string is mentioned for these
particular snippets and nowhere else?
I'm guessing, but I think these are the only examples that purport to be
"complete" LP programs. Everything else are just snippets of code.

The other possibility is that these were written by Graham, I think,
whereas I wrote most of the others.
According to the git history, you wrote it in 2007, but these days
the 'addversion' option did not exist.

This option was added by John Mandereau in February 2008

In April 2008, John adjusted your snippet to use the 'addversion' option.

However, the history also states that 'addversion' was removed from
two snippets in January 2016 with
by Greg Swinford.

I don't think it would be a problem if the version strings were dropped,
I would like to support this opinion.
The 'addversion' option, as it is now, is useless for end users, because
it relies on
the @version macro to be defined.

So we could either
1. Drop the support for 'addversion' in lilypond-book completely
2. Let lilypond-book prepend the version string to verbatim snippets
depending on the version it uses for compiling the snippet, not
on the @version macro. (if this is possible without a major rewrite)

IMHO, the graphical output and version string should match.
I do not know, if somebody actually compiles the documentation
with a precompiled lilypond/lilypond-book. But with the current setup
it could happen that a snippet is compiled with a
lilypond version different from the \version string and the
conclusion: "Alright, this snippets looks that particular way if compiled
with lilypond 2.x.x." would be misleading.

Please correct me if I have some wrong thinking here.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]