[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: conversion rule for set-octavation/ottava with wrong version number?
From: |
Alex Schreiber |
Subject: |
Re: conversion rule for set-octavation/ottava with wrong version number? |
Date: |
Wed, 1 Nov 2017 14:44:04 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 |
On 2017-11-01 10:51, David Kastrup wrote:
>
> I don't really agree: that way lies madness. Do we take the time when
> something stops working reliably, or the time when it stops working
> altogether? I do try to keep rules "idempotent" as much as possible,
> making it harmless to apply them multiple times in a row. That allows
> just trying another sweeping convert-ly run. But this isn't really
> possible for all rules.
>
Thank you, David, your argument is convincing.
But in retrospective, it would have been nice if the old compiler
version had given a deprecation warning.
In case somebody uses a search engine for
error: GUILE signaled an error for the expression beginning here
#
(set-octavation 1)
Unbound variable: set-octavation
and ends up here :)
then you should either try
convert-ly --from=2.11.54 ...
or manually do the change
#(set-octavation oct) -> \ottava #oct