You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Place minibuffer at the top of the current frame on read-from-minibuffer.
While it's fine for me to have eldoc, flymake and other messages to appear at the bottom of the screen, editing minibuffer (find file, create VC branch, etc.) feels more comfortable in the upper area of the screen.
mini-frame-mode makes an advice around read-from-minibuffer function to create and show minibuffer-only child frame to accept input.
How it looks like
By default mini-frame is placed at the top of the current frame and occupies full width. Here is execute-extended-command (M-x) with icomplete-mode enabled:
Those who use vertical completion candidates list may configure mini-frame not to occupy full width:
Until this issue will be solved, Gnome Shell users must also set mini-frame height.
Another option for Gnome Shell users is to use the following code in initialization file:
(setq x-gtk-resize-child-frames 'resize-mode)
Ignore commands
One can configure the list of commands that must not be shown in the child frame by customizing the mini-frame-ignore-commands. The eval-expression command is there by default because mini-frame have no modeline to display eldoc hints. And because there must be some place to turn mini-frame-mode off if something goes wrong (I hope not) :)