Feature request: helm-initial-inputs-alist

[leungbk]

Is your feature request related to a problem? Please describe.
For a handful of functions, I wind up typing ^ quite often into the minibuffer.

Describe the solution you'd like
Some sort of defcustom, helm-initial-inputs-alist to allow the user to specify an initial input in the helm minibuffer for a function. Ivy already has this.

[whudwl]

I would also like this.

[BettaGeorge]

As a workaround, you know you can just write to the minibuffer, right? I have functions like this, I just hook a custom input into them before the user gets a chance to type in the minibuffer.

[whudwl]

As a workaround, you know you can just write to the minibuffer, right? I have functions like this, I just hook a custom input into them before the user gets a chance to type in the minibuffer.

which hook do you use?

[BettaGeorge]

As a workaround, you know you can just write to the minibuffer, right? I have functions like this, I just hook a custom input into them before the user gets a chance to type in the minibuffer.

which hook do you use?

It kind of depends on what exactly you want to achieve. For helm sources, I usually just hook into :init with something like this:

            (save-excursion
              (select-window (active-minibuffer-window))
              (if (< 0 (length (minibuffer-contents))) (kill-whole-line))
              (insert "your favourite string")
    	    )

Ignore the kill-whole-line part if your use case never has stuff in the minibuffer beforehand. I have it here because the same code is called when I do custom fuzzy completion, which I want to empty the misspelt command first.