completing-read-multiple behaves as if REQUIRE-MATCH were non-nil

[tarsius]

When ivy-mode is enabled, completing-read-multiple always behaves as if its REQUIRE-MATCH argument were non-nil.

[abo-abo]

ivy-mode does this:

(when ivy-do-completion-in-region
  (setq completion-in-region-function 'ivy-completion-in-region))

completing-read-multiple calls read-from-minibuffer. While in the minibuffer, TAB calls completion-in-region-function.

At this point, require-match is not passed from anywhere. I set it to t since my most common use of TAB is during eval-expression, and :require-match t makes sense in that case.

It's easy to change to require-match nil, but this results in a loss of convenience during eval-expression. Suggestions welcome.

[tarsius]

I'll look into it, if you don't come up with something first. But I probably won't get to it soon. Could you please assign this issue to me, so that it shows up in my version of https://github.com/issues/assigned.

[tarsius]

Maybe :require-match (not (eq (current-local-map) crm-local-completion-map)) would work. But I don't know anymore why I thought that it was necessary that ivy-completing-in-region did not just always use t. I can enter arbitrary values even without this, provided I do it before pressing TAB.

[abo-abo]

I'm still not sure how ivy-completion-in-region should perform if the input did not match any of the candidates.
Since the completion was initiated for the prefix, the prefix is now erased and the new thing is inserted. I wonder if the prefix should be kept.
On the other hand, keeping the prefix is just equivalent to canceling the completion and typing the thing in manually.

[tarsius]

I am also quite unsure what the best approach is... Ah, well.