Viper messing up minibuffer (was Re: [vimpulse] Bug: TAB doesn't autocomplete in minibuffer.)

Štěpán Němec stepnem at
Fri Jul 2 18:53:17 CEST 2010

On Fri, Jul 02, 2010 at 05:28:29PM +0100, Alessandro Piras wrote:
> What does that hook do exactly? I may be interested :-)

Well, just have a look yourself -- I don't remember any more. :-)
AFAIR it does all Viper's minibuffer setup, e.g. that horrible
greenish/orangeish colour etc. What I wanted was to have the normal
Emacs minibuffer, and removing that function from the hook did it.
Having multiple modes in the minibuffer seemed a bit over the top to me,
and IIRC I had also some problems with keybindings (Ido mode) etc.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on Usenet and in e-mail?

> On 2 July 2010 16:57, Štěpán Němec <stepnem at> wrote:
> > Somewhat off-topic, I've found Viper's messing with minibuffer
> > intolerable, have put the following in my init file:
> >
> > (remove-hook 'minibuffer-setup-hook 'viper-minibuffer-setup-sentinel)
> >
> > ... and live happily ever since ;-)
> >
> > (I also set viper-vi-style-in-minibuffer to nil before, don't remember
> > if it still matters after removing the hook.)

More information about the implementations-list mailing list