rizumu <
funk...@gmail.com> writes:
> Hi Thierry,
>
> Thanks for the reply. What you've said works great, but I didn't explain
> myself clearly about the tab completion part. I'd like to know how it works
> inside of the helm mini-buffer, not a code file, but that is useful to know
> as well.
>
> If I have helm-mode enabled and type "M-x eval-b <tab>" nothing happens, I
> just get the "Sole action: action-fn" message in the minibuffer. Since
> there are no other completions for "eval-b" except for "eval-buffer" I
> thought it would tab complete and select this command. Instead I have to
> press enter.
>
> Similarly for "M-x find-file ~/.emacs.d/ini <tab>" I expected it to tab
> complete and open init.el. And on that note, if there is a match such as
> two folders "~/file1.el" "~/file2.el" typing "~/fi <tab>" should complete
> up until to "~/file" and wait for me to type a 1 or 2, press tab again, and
> then open that file.
>
> Probably I'm missing something simple, but thats how bash completion works,
> so I'd like to achieve the same behavior inside of helm.
In helm <TAB> open the action buffer if the source have more than one
action.
helm-M-x have only one action, if you use helm-mode the regular M-x
command will have only one action also.
A typical use of helm is typing something in minibuffer to narrow down
the completion buffer and moving in this buffer with arrow keys or C-n/p
to select the candidate you need.
So to reply to your question, there is no TAB completion in helm because
the helm-buffer is the completion result itself.