Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott writes: > On Tue, Oct 17, 2017 at 01:58:16PM -0500, David Wright wrote: >> On Tue 17 Oct 2017 at 11:31:46 (-0700), Paul Scott wrote: >> > On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: > > Thank you for your explanation and I believe I have long

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 01:58:16PM -0500, David Wright wrote: > On Tue 17 Oct 2017 at 11:31:46 (-0700), Paul Scott wrote: > > On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: > > > Paul Scott writes: > > > > > > > On Tue, Oct 17, 2017 at 08:03:44PM +0200,

Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott writes: > On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: >> Paul Scott writes: >> >> > On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: >> >> >> >> That is the whole _point_ of a warning: LilyPond is able

Re: \version statement, etc.

2017-10-17 Thread David Wright
On Tue 17 Oct 2017 at 11:31:46 (-0700), Paul Scott wrote: > On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: > > Paul Scott writes: > > > > > On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: > > >> > > >> That is the whole _point_ of a

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 11:31:46AM -0700, Paul Scott wrote: > On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: > > Paul Scott writes: > > > > > On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: > > >> > > >> That is the whole _point_ of a

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: > Paul Scott writes: > > > On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: > >> > >> That is the whole _point_ of a warning: LilyPond is able to complete > >> the job which _may_ mean that it

Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott writes: > On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: >> >> That is the whole _point_ of a warning: LilyPond is able to complete >> the job which _may_ mean that it works perfectly but it cannot be >> sure. For example, because it does not

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: > Paul Scott writes: > > > On Tue, Oct 17, 2017 at 07:42:42PM +0200, David Kastrup wrote: > >> Paul Scott writes: > >> > >> > On Tue, Oct 17, 2017 at 06:51:37PM +0200, David Kastrup

Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott writes: > On Tue, Oct 17, 2017 at 07:42:42PM +0200, David Kastrup wrote: >> Paul Scott writes: >> >> > On Tue, Oct 17, 2017 at 06:51:37PM +0200, David Kastrup wrote: >> >> Paul Scott writes: >> >> >> >> >

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 07:42:42PM +0200, David Kastrup wrote: > Paul Scott writes: > > > On Tue, Oct 17, 2017 at 06:51:37PM +0200, David Kastrup wrote: > >> Paul Scott writes: > >> > >> > \include brings the version warning as follows: > >> > >

Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott writes: > On Tue, Oct 17, 2017 at 06:51:37PM +0200, David Kastrup wrote: >> Paul Scott writes: >> >> > \include brings the version warning as follows: >> > >> > To avoid changing the version on each of my many .ly files >> >> You

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 06:51:37PM +0200, David Kastrup wrote: > Paul Scott 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

Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott 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.

Re: \version statement, etc.

2017-10-17 Thread Paul Scott
On Tue, Oct 17, 2017 at 04:54:47PM +0200, David Kastrup wrote: > Paul Scott writes: > > > I may be downloading while changes are in progress. > > > > I just downloaded and installed 2.19.80 (what happened to 2.19.66 through > > 2.19.79?) > > > > 2.19.80 doesn't seem to

Re: \version statement, etc.

2017-10-17 Thread David Kastrup
Paul Scott writes: > I may be downloading while changes are in progress. > > I just downloaded and installed 2.19.80 (what happened to 2.19.66 through > 2.19.79?) > > 2.19.80 doesn't seem to see my version statements: > > plentyr3.ly:1: warning: no \version statement

Re: \version statement, etc.

2017-10-17 Thread Phil Holmes
- Original Message - From: "Paul Scott" <waterho...@ultrasw.com> To: "LilyPond User List" <lilypond-user@gnu.org> Sent: Tuesday, October 17, 2017 7:31 AM Subject: \version statement, etc. I may be downloading while changes are in progress. Should ha

Re: \version statement, etc.

2017-10-17 Thread Malte Meyn
Am 17.10.2017 um 08:31 schrieb Paul Scott: I just downloaded and installed 2.19.80 (what happened to 2.19.66 through 2.19.79?) 2.19.80 is the first pre-release for 2.20; the xx in 2.19.xx approaching 99 stands for “we’ll be there soon”. 2.19.80 doesn't seem to see my version statements:

Re: \version statement, etc.

2017-10-17 Thread Simon Albrecht
On 17.10.2017 08:31, Paul Scott wrote: I may be downloading while changes are in progress. I just downloaded and installed 2.19.80 (what happened to 2.19.66 through 2.19.79?) They were skipped, since we’re in the process of preparing the 2.20 release. 2.19.80 doesn't seem to see my version

\version statement, etc.

2017-10-17 Thread Paul Scott
I may be downloading while changes are in progress. I just downloaded and installed 2.19.80 (what happened to 2.19.66 through 2.19.79?) 2.19.80 doesn't seem to see my version statements: plentyr3.ly:1: warning: no \version statement found, please add \version "2.19.80" for future