+++ Jason Spiro [Jul 29 09 19:18 ]:
On Wed, Jul 29, 2009 at 3:34 PM, John MacFarlane <[email protected]> wrote:
I'm using the latest version from the wiki, with a recent emacs-snapshot (emacs 23 from CVS via http://emacs.orebokech.com/) and gnome-terminal. (But I tried just it with xterm as well, with the same results.) I'm not sure what "the multi file setup" refers to, but I'm not doing anything special in my .emacs: just
(setq viper-mode t) ; enable Viper at load time (setq viper-ex-style-editing nil) ; can backspace past start of insert / line (require 'viper) ; load Viper (setq vimpulse-experimental nil) ; don't load bleeding edge code (see 6. installation instruction) (require 'vimpulse) ; load Vimpulse (setq woman-use-own-frame nil) ; don't create new frame for manpages (setq woman-use-topic-at-point t) ; don't prompt upon K key (manpage display)
(require 'redo) ; enables C-r (redo key) (require 'rect-mark) ; enables nice-looking block visual mode
Best, John
Try using an otherwise-empty .emacs -- remove all lines except the ones you mentioned above. Does that work?
I tried using -q to suppress loading of .emacs, and just loading the vimpulse stuff manually. No change. I tried it with emacs 22. That didn't help. I even tried it in a console. No change. But then I noticed something -- visual mode actually *does* work when I move the cursor using hjkl. But when I use the arrow keys, it causes vimpulse to leave visual mode. Visual mode works fine with arrow keys when I run gtk emacs. One more clue: when this happens, if you check *Messages*, it contains the line: Toggling vimpulse-visual-mode off; better pass an explicit argument. This seems to be caused by the use of arrow keys. Best, John