bug#56613: 29; minibuffer-complete-history throws an error for minibuffer-history-variable=t

[Daniel Mendler]

On 7/18/22 17:04, Stefan Monnier wrote:
>> Doesn't it work if you retrieve the boundaries first with
>> `completion-boundaries` from `minibuffer-completion-table`? In my
>> Vertico package I use the following code and it works without issues
>> with CRM. The API requires a little bit of a ceremony.
> 
> I suspect it won't work correctly when CRM is used with a completion
> table that itself uses boundaries (e.g. when completing a list of file
> names).
> 
> It's quite unusual, so in practice your approach probably works fine,
> but fundamentally I think it's "wrong" (tho I don't have much better to
> offer right now, except by adding CRM-specific hacks).
Yes, I've suspected that this is an issue. But CRM of
completion-file-name-table works well with Vertico.

(completing-read-multiple "Files: " #'completion-file-name-table)

On the other hand read-file-name-internal or completion--file-name-table
do not work. I get some args-out-of-range errors due to the quoting
mechanism.

(completing-read-multiple "Files: " #'read-file-name-internal)

Daniel