lilypond-user
[Top][All Lists]
Advanced

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

Re: \version statement, etc.


From: Paul Scott
Subject: Re: \version statement, etc.
Date: Tue, 17 Oct 2017 10:56:34 -0700
User-agent: NeoMutt/20170609 (1.8.3)

On Tue, Oct 17, 2017 at 07:42:42PM +0200, David Kastrup wrote:
> Paul Scott <address@hidden> writes:
> 
> > On Tue, Oct 17, 2017 at 06:51:37PM +0200, David Kastrup wrote:
> >> Paul Scott <address@hidden> writes:
> >> 
> >> > \include brings the version warning as follows:
> >> >
> >> > To avoid changing the version on each of my many .ly files
> >> 
> >> You aren't supposed to change the version on each of your many .ly
> >> files: that would be pointless since that doesn't upgrade the syntax.
> >> You are supposed to update them with convert-ly.
> >> 
> >> convert-ly -ed *.ly
> >> 
> >> will do the job.
> >
> > Thank you for replying.
> >
> > This has nothing to do with convert-ly.
> 
> Why?

It has to do will all the Lily projects.  I certainly appreciate all the
work on convert-ly and I keep my code current anyway.

Does LilyPond use the version statements for more than just convert-ly?

> > This is how I set up all my projects for efficient (from my point of
> > view) editing.
> 
> So?

So, why does my minimal example give a warning even though it works
perfectly?  Which means all of my projects will give that warning even
though they work.

Paul





reply via email to

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