Adding consult--force to minibuffer content interactively?

[armindarvish]

@minad I have been trying to create a function that adds the consult--foce property to the minibuffer contents with the aim to bind it in the minibuffer-local-map, so I can force a consult-async process (e.g. grep) to fetch results when the input is shorter than 'consult-async-min-input' with a key binding. But all my attempts so far have failed. It appears that the property gets stripped before the string gets to consult--async-min-input.

Below is an example of the function I have tried

(defun my:consult-force ()
    (interactive)
    (when (minibuffer-window-active-p (selected-window))
      (save-excursion
        (when (and (minibuffer-contents) (> (length (minibuffer-contents)) 1))
        (let* ((beg (beginning-of-visual-line))
               (end (+ beg 2)))
          (put-text-property beg end 'consult--force t))))))

I even tried inserting propertized text and that did not work either. Here is a screenshot:

Any suggestions for how I may be able to implement this? or is this not possible (e.g. because of minibuffer and completing-read limitations)?

[minad]

consult--force is an internal property of the splitter and handled by consult--async-min-input. I think it would be better to figure out a way which fits better to the API instead of trying to "hack" it somehow. In consult-omni I wonder if you can use consult--multi as provided by Consult now, since there still seems to be a lot of code duplication and custom code for static/dynamic/async sources.

[armindarvish]

consult--force is an internal property of the splitter and handled by consult--async-min-input. I think it would be better to figure out a way which fits better to the API instead of trying to "hack" it somehow.

Well, I don't see any direct path for forcing the consult-async right now, and I thought maybe consult--force would be a good candidate to play around with. So, I guess the question for you would then then be "what do you think about adding the capability to be able to force consult-async with some command/keybinding in the minibuffer"? This can for example be a global variable in the or statement inside consult--async-min-input here:

(or (and (not (equal action ""))
                                     (get-text-property 0 'consult--force action))
                                (>= (length action) min-input))

The variable can be switched to t with a command and has to be reset back to nil when consult is exited; or maybe an entire new function that is called before the consult--async-min-input in the pipeline.

In consult-omni I wonder if you can use consult--multi as provided by Consult now, since there still seems to be a lot of code duplication and custom code for static/dynamic/async sources.

Oh, yes, I just haven't had any time to go through that. I just pushed some quick fixes, so consult-omni works with the new API, but I still have to go back and simplify things using the new consult-multi. I think some of the duplication, I will keep because they allow a simple and unified way of adding new sources without worrying about what happens under the hood with async vs. non-async sources, but I have to find time to go through it and see what parts I'd want to keep/change.