From: Michael Brand <michael.ch.brand@gmail.com>
To: "Andrew J. Korty" <ajk@iu.edu>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [OT] Have you also got hooked by Vim?
Date: Thu, 13 Jan 2011 15:42:44 +0100 [thread overview]
Message-ID: <AANLkTikBYwPT4M3XEFf6od=ariLzM=5Q0Ln4FDZ3Upth@mail.gmail.com> (raw)
In-Reply-To: <22132.1294921626@iu.edu>
Hi Andrew
On Thu, Jan 13, 2011 at 13:27, Andrew J. Korty <ajk@iu.edu> wrote:
> I've tried several times to use Viper, but I always give up. The usual
> showstopper is read-only Emacs modes with single-character key bindings,
> like MH-E. The d key deletes a message in an MH folder, but in vi, d
> deletes text to a target. So the obvious thing to do is turn Viper mode off
> in folder buffers. But I'd like to use the vi keys for motion (h, j, k, l)
> -- I can't get used to using them in some buffers and not others. So unless
> I'm unaware of some trick, I have to build my own keymap almost for each of
> these modes.
I hope I understand you right and this helps: I use C-z for this with
viper level 3 to have C-z bound to Emacs. When I open e. g. dired then
the viper state in this buffer that is shown in the mode line is <E>
meaning Emacs. In this mode the Emacs keys are active like e. g. `f'
to open the file in a new buffer or p/n to go up/down. Back in dired
and after C-z the viper state changes to <V> meaning viper. In this
mode the vi keys are active like e. g. `f' to find a certain character
or k/j to go up/down. C-z at any time toggles again to <E>.
Michael
next prev parent reply other threads:[~2011-01-13 14:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 6:09 [OT] Have you also got hooked by Vim? Marcelo de Moraes Serpa
2011-01-13 6:48 ` Michael Brand
2011-01-13 7:32 ` Detlef Steuer
2011-01-13 8:34 ` Michael Brand
2011-01-13 12:28 ` Filippo A. Salustri
2011-01-13 12:27 ` Andrew J. Korty
2011-01-13 14:42 ` Michael Brand [this message]
2011-01-13 16:58 ` Eric S Fraga
2011-01-13 18:33 ` Marcelo de Moraes Serpa
2011-01-13 19:52 ` Matt Lundin
2011-01-13 20:04 ` Nick Dokos
2011-01-13 20:39 ` Tommy Stanton
2011-01-20 0:02 ` Dan Davison
2011-01-20 0:11 ` Martin Weigele
2011-01-20 2:51 ` Matt Lundin
2011-01-20 4:36 ` Jeff Horn
2011-01-20 8:24 ` Shelagh Manton
2011-01-20 12:20 ` Matt Lundin
2011-01-20 16:00 ` Eric S Fraga
2011-01-20 8:09 ` Michael Markert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikBYwPT4M3XEFf6od=ariLzM=5Q0Ln4FDZ3Upth@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=ajk@iu.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).