From: "Lawrence Velázquez" <larryv@macports.org>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-workers@zsh.org
Subject: Re: PATCH: default vi-mode key bindings
Date: Fri, 5 Dec 2014 13:55:22 -0500 [thread overview]
Message-ID: <A3434BD7-805A-42A5-B2F2-F87313B0E0AF@macports.org> (raw)
In-Reply-To: <5481EF6D.4060800@eastlink.ca>
On Dec 5, 2014, at 12:46 PM, Ray Andrews <rayandrews@eastlink.ca> wrote:
> Ok, but is any of that actually used at the command line?
"The command line" doesn't dictate what keys ought to be used to move about and edit text.
> Does anyone need/use 'command mode' when typing a simple command?
>
> $ grep "The falcon cannot hear the falconer;" /Yeats/*
>
> What would one do with command mode there?
Edit the command in a way that one is comfortable with? Not everyone likes Emacs keybindings.
> Editing a novel, of course, but a command line? Or does this mean that zsh somehow butts itself right in to vi so that when editing a novel, 'vi-style' as set by zsh is somehow active? Is that polite?
I'm pretty sure one has to enable vi mode explicitly. Then, I presume one has a command mode and an insert mode, as expected.
> And then there's vim mode too but that's different from vi mode? I'm missing something fundamental here.
There is no vim mode; that was Bart musing. The issue is whether zsh should cater to people who know vim but not vi.
vq
next prev parent reply other threads:[~2014-12-05 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 18:28 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 [this message]
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
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=A3434BD7-805A-42A5-B2F2-F87313B0E0AF@macports.org \
--to=larryv@macports.org \
--cc=rayandrews@eastlink.ca \
--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).