Subject: bug#43598: replace-in-string: finishing touches

From: Mattias Engdegård <[email-masked]>
Date: Fri, 25 Sep 2020 13:22:41 +0200

25 sep. 2020 kl. 13.11 skrev Lars Ingebrigtsen <[email-masked]>:

> It all looks good to me; please apply.

Thanks, will do shortly.

> Right, so if the multibyteness differs, then do another check to see
> whether both strings are all-ASCII anyway, and do the comparison without
> conversion...

Both strings don't need to be all-ASCII; one of them suffices.

By the way, I added an argument check to replace-in-string to prevent it from entering an infinite loop.