Re: [PATCH] Handle case where `beg` and `end` are strings instead of markers

[Juri Linkov]

> Hm, while my patch does fix the error I was seeing, it makes completing
> multiple items with completing-read-multiple not properly insert
> subsequent completions.
>
> I also note that I only saw the aberrant behaviour while using functions
> that used CRM, so perhaps there's a more underlying cause and/or better
> place to fix this.

Please describe how do you expect this should behave from a UI point of view.
I see that when using on a simple call:

  (completing-read-multiple "Tags: " '(("tag1") ("tag2") ("tag3")))

subsequent completions can be selected properly
after replacing these lines in your patch

+                 (+ (search-forward beg)
+                    (length beg)))))

with

+                 (search-forward beg))))