Re: strange replacement 100 → hundred in NR

[David Kastrup]

Jonas Hahnfeld <hahnjo@hahnjo.de> writes:

> Am Donnerstag, den 01.10.2020, 14:07 +0200 schrieb David Kastrup:
>> Jonas Hahnfeld <hahnjo@hahnjo.de> 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 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...
>> > 
>> > As far as I understand, the correct solution is to reset text-font-
>> > defaults per session.
>> 
>> No, the correct solution is not to use assq-set! on shared variables,
>> and variables accessible to \override are shared.
> Yes, that is what's needed to actually make the session variable work.
> I'm now doing assoc-set! on (alist-copy text-font-defaults), see the
> MR. Is that what you're saying?

I think it would be saner to use acons here rather than assoc-set!.

-- 
David Kastrup