[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 48 and 72 ET
From: |
David Kastrup |
Subject: |
Re: 48 and 72 ET |
Date: |
Fri, 10 Feb 2017 08:40:02 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Simon Albrecht <address@hidden> writes:
> On 10.02.2017 00:19, Hans Åberg wrote:
>> If LilyPond knows how to run the code via convert-ly, why does it not do it?
>
> LilyPond itself doesn’t change the code it is reading. convert-ly is a
> separate Python script.
> It might be a valid feature request, though, to have a command-line
> option which makes LilyPond call convert-ly, if the \version statement
> points to an older version, and then read the resulting code.
> That would leave some things to be designed though, e.g. what would
> happen if convert-ly issues ‘Not smart enough to update…’ – which
> happens?
The problem is more that point-and-click and error messages no longer
correspond to the actual source code.
--
David Kastrup
- Re: 48 and 72 ET, (continued)
- Re: 48 and 72 ET, David Kastrup, 2017/02/09
- Re: 48 and 72 ET, Hans Åberg, 2017/02/10
- Re: 48 and 72 ET, David Kastrup, 2017/02/10
- Re: 48 and 72 ET, Hans Åberg, 2017/02/10
- Re: 48 and 72 ET, mskala, 2017/02/09
- Re: 48 and 72 ET, Hans Åberg, 2017/02/09
- Re: 48 and 72 ET, Simon Albrecht, 2017/02/09
- Re: 48 and 72 ET,
David Kastrup <=
- Re: 48 and 72 ET, Hans Åberg, 2017/02/10
- Re: 48 and 72 ET, David Kastrup, 2017/02/09
- Re: 48 and 72 ET, mskala, 2017/02/09
- Re: 48 and 72 ET, Hans Åberg, 2017/02/10
- Re: 48 and 72 ET, David Kastrup, 2017/02/10
- Re: 48 and 72 ET, Hans Åberg, 2017/02/10
- Re: 48 and 72 ET, David Kastrup, 2017/02/10
- Re: 48 and 72 ET, Hans Åberg, 2017/02/10
Re: 48 and 72 ET, Thomas Richter, 2017/02/10