Am Donnerstag, den 01.10.2020, 16:03 +0200 schrieb Michael Käppler:
> Am 01.10.2020 um 12:24 schrieb Jonas Hahnfeld via Discussions on
> LilyPond development:
> > So I think it's more likely that the issue got exposed by
> > commit 5a957021a3 which runs lilypond once per document passed to
> > lily
Am 01.10.2020 um 12:24 schrieb Jonas Hahnfeld via Discussions on
LilyPond development:
So I think it's more likely that the issue got exposed by
commit 5a957021a3 which runs lilypond once per document passed to
lilypond-book instead of per included file. This increases the chance
of being unlucky
Jonas Hahnfeld writes:
> Am Donnerstag, den 01.10.2020, 14:07 +0200 schrieb David Kastrup:
>> Jonas Hahnfeld writes:
>>
>> > Am Donnerstag, den 01.10.2020, 05:07 +0200 schrieb Werner LEMBERG:
>> > > > > what was the last version in which this was seen working as
>> > > > > expected?
>> > >
>>
Am Donnerstag, den 01.10.2020, 14:07 +0200 schrieb David Kastrup:
> Jonas Hahnfeld writes:
>
> > Am Donnerstag, den 01.10.2020, 05:07 +0200 schrieb Werner LEMBERG:
> > > > > what was the last version in which this was seen working as
> > > > > expected?
> > >
> > > For me, three weeks ago.
> > >
Jonas Hahnfeld writes:
> Am Donnerstag, den 01.10.2020, 05:07 +0200 schrieb Werner LEMBERG:
>> >> 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.
>
> So I
Am Donnerstag, den 01.10.2020, 05:07 +0200 schrieb Werner LEMBERG:
> >> 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.
So I think it's more likely that the issue
>> 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
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
[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
11 matches
Mail list logo
