>> what was the last version in which this was seen working as
>> expected?
For me, three weeks ago.
> Probably never did but people got lucky.
Yes, it looks like that.
Werner
On Sep 30, 2020, at 15:56, Michael Käppler wrote:
>
> Am 29.09.2020 um 14:38 schrieb Dan Eble:
...
>> I lean toward removing the warning.
> Hi Dan,
> what about this: (only tested with your MWE, though)
Thanks & LGTM. Are you willing to put that in a merge request?
—
Dan
Han-Wen Nienhuys writes:
> On Wed, Sep 30, 2020 at 10:11 PM Han-Wen Nienhuys wrote:
>
>>
>>
>> On Wed, Sep 30, 2020 at 8:05 PM Werner LEMBERG wrote:
>>
>>>
>>> [git 9c3803fba4960b4afa63baeb50201a0cfa48f8f1]
>>>
>>> I've just built the whole documentation, and I get a strange string
>>> replacem
On Wed, Sep 30, 2020 at 10:11 PM Han-Wen Nienhuys wrote:
>
>
> On Wed, Sep 30, 2020 at 8:05 PM Werner LEMBERG wrote:
>
>>
>> [git 9c3803fba4960b4afa63baeb50201a0cfa48f8f1]
>>
>> I've just built the whole documentation, and I get a strange string
>> replacement in Appendix A of the NR (from file
On Wed, Sep 30, 2020 at 8:05 PM Werner LEMBERG wrote:
>
> [git 9c3803fba4960b4afa63baeb50201a0cfa48f8f1]
>
> I've just built the whole documentation, and I get a strange string
> replacement in Appendix A of the NR (from file
> `markup-list-commands.texi`), see attached image.
>
As far as I remem
Am 29.09.2020 um 14:38 schrieb Dan Eble:
Using the latest version of master, I'm seeing the warning "Could not find
ottavation markup for 1 octaves up" in a number of my scores when MIDI output is
enabled. This warning was added about a year ago in commit
476194c706e4f9898fdbd5847dc1a924843f0
[git 9c3803fba4960b4afa63baeb50201a0cfa48f8f1]
I've just built the whole documentation, and I get a strange string
replacement in Appendix A of the NR (from file
`markup-list-commands.texi`), see attached image.
As far as I remember, this didn't happen previously. Is it possible
that this code
