Re: Warning when defining variables on the command line

2019-11-19 Thread Aaron Hill
On 2019-11-19 10:58 am, Matt Wallis wrote: So, I have added the line (in place of your call to format): subtitle = #(guile-user-lookup 'subtitle "...") in order to get back into the world of lilypond variables, and it all works. As you discovered, you do need to explicitly define a new

Re: Warning when defining variables on the command line

2019-11-19 Thread Matt Wallis
On 19/11/2019 15:39, Aaron Hill wrote: On 2019-11-19 3:37 am, Matt Wallis wrote: I want to pass the subtitle into lilypond on the command line because it is also required by other programmes (e.g. sox needs the subtitle to create a tag for the mp3 it creates). [ . . . ] But I now get the

Re: Warning when defining variables on the command line

2019-11-19 Thread Aaron Hill
On 2019-11-19 3:37 am, Matt Wallis wrote: I want to pass the subtitle into lilypond on the command line because it is also required by other programmes (e.g. sox needs the subtitle to create a tag for the mp3 it creates). [ . . . ] But I now get the warning: Parsing...WARNING: #f: imported

Warning when defining variables on the command line

2019-11-19 Thread Matt Wallis
I want to pass the subtitle into lilypond on the command line because it is also required by other programmes (e.g. sox needs the subtitle to create a tag for the mp3 it creates). Looking at