From: Christian Neukirchen <chneukirchen@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: vi mode question.
Date: Sun, 07 Dec 2014 01:32:40 +0100 [thread overview]
Message-ID: <87sigs47vb.fsf@gmail.com> (raw)
In-Reply-To: <548386E2.6050504@eastlink.ca> (Ray Andrews's message of "Sat, 06 Dec 2014 14:44:50 -0800")
Ray Andrews <rayandrews@eastlink.ca> writes:
> On 12/06/2014 02:09 PM, Bart Schaefer wrote:
>> Anyone who knows vi(m) will already know this, but for Ray et al.:
> ...
>
> Thanks for that. I wonder why there isn't (*if* there isn't) a compromise:
> All the most basic editing/moving primitives working in insert mode
> like emacs or
> the (what DOS/Windows people would call) 'normal' human editors, but
> still having a command mode for the complexities (where emacs goes
> nuts with all those combinations). You'd mostly be in 'normal' mode, but
> when you needed to do some heavy lifting, 'command mode' would still
> be there. I haven't tried vi for a long time, I should try again.
bindkey -e
bindkey '^[' vi-cmd-mode
Effectively combines emacs as insert-mode with vi as command mode.
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
next prev parent reply other threads:[~2014-12-07 0:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 18:28 PATCH: default vi-mode key bindings Oliver Kiddle
2014-12-05 7:17 ` Bart Schaefer
2014-12-05 7:35 ` Mikael Magnusson
2014-12-05 7:56 ` Jan Larres
2014-12-05 13:26 ` Oliver Kiddle
2014-12-05 17:46 ` Ray Andrews
2014-12-05 17:59 ` Eric Cook
2014-12-05 18:04 ` richo
2014-12-05 18:55 ` Lawrence Velázquez
2014-12-05 20:29 ` vi mode question Ray Andrews
2014-12-05 21:04 ` Lawrence Velázquez
2014-12-06 22:09 ` Bart Schaefer
2014-12-06 22:44 ` Ray Andrews
2014-12-07 0:32 ` Christian Neukirchen [this message]
2014-12-07 5:02 ` Ray Andrews
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sigs47vb.fsf@gmail.com \
--to=chneukirchen@gmail.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).