GNU bug report logs -
#1072
23.0.60; can't exit viper insert mode with ESC using emacsclient -t
Previous Next
Full log
Message #25 received at 1072 <at> emacsbugs.donarmstrong.com (full text, mbox):
It is
(viper--intercept-key-maps viper--key-maps)
but it does not look like this kicks in.
The value of viper--intercept-key-maps is
((viper-vi-intercept-minor-mode keymap
(escape . viper-intercept-ESC-key)
(26 . viper-toggle-key-action))
(viper-insert-intercept-minor-mode keymap
(escape . viper-intercept-ESC-key))
(viper-emacs-intercept-minor-mode keymap
(26 . viper-change-state-to-vi)))
So, the keymaps are set correctly, but they do not seem to kick in.
michael
On Tue, 07 Oct 2008 18:21:40 +0200
"Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> wrote:
> Stefano Zacchiroli wrote:
> >> The key different seems to be key binding, while in main Emacs and
> >> framed client "C-h k ESC" returns (viper-intercept-ESC-key), in
> >> console clients "C-h k ESC" hangs showing "ESC-" waiting for the
> >> next key in the binding.
> >
> > Does this blink some light? (Or maybe explains that the bug is not at
> > all related to Viper and need to be looked for in some emacsclient
> > detail?)
>
> What is the value of emulation-mode-map-alists in both cases? Is
> viper--intercept-key-maps there in both cases?
>
> What is the value of this variable in both cases? It should be something
> like
>
> ((viper-vi-intercept-minor-mode keymap
> (f6 . viper-toggle-key-action)
> (escape . viper-intercept-ESC-key)
> (26))
> (viper-insert-intercept-minor-mode keymap
> (escape . viper-intercept-ESC-key))
> (viper-emacs-intercept-minor-mode keymap
> (f6 . viper-change-state-to-vi)
> (26)))
>
> What is the values of the key variables in the association list?
>
> > Thanks a lot!
> > Cheers.
> >
>
This bug report was last modified 16 years and 237 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.