Tom Cloyd <tomcloydm...@gmail.com> writes: > On 12/30/2013 05:13 PM, David Kastrup wrote: >> Noeck <noeck.marb...@gmx.de> writes: >> >>> Am 31.12.2013 00:35, schrieb Eluze: >>>> Tom Cloyd-2 wrote >>>>> Running convert-ly (from Frescobaldi) on a score, I get this at the top >>>>> of the code: >>>>> >>>>> \version "2.17.97" >>> I can confirm this using version 2.18.0 (both within Frescobaldi and on >>> the commandline). I also would have expected 2.18.0 after the conversion. >> It's due to a miscommunication between myself and Phil. This is >> harmless though a bit of a nuisance. Most of the time, you'll want to >> use the -d option anyway to avoid declaring a larger version than >> necessary: in that case this oversight will not have an effect. >> >> If you want to really have the version display converted to 2.18.0, you >> can use -t 2.18.0 I think. >> >> This will be fixed with 2.18.1 which I expect to take perhaps a month to >> arrive. I think I'll be pushing the fix to both stable and development >> branches soonish, so it will appear in 2.19.0 as well. >> > "harmless" - thanks for the confirmation. > > As for "the -d option", I find this in the console output for "lilypond -h"; > > -d, --define-default=SYM[=VAL] set Scheme option SYM to VAL > (default: #t). > Use -dhelp for help. > > Regrettably, that's not language for mere mortals, so I can't make any > sense of it.
The options are described in the "Using LilyPond" manual, and I was talking about the -d option to convert-ly rather than to lilypond. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
