From: Erik Soderquist <ErikSoderquist@gmail.com>
To: cygwin@cygwin.com
Subject: Re: updated vim broke arrow/delete keys
Date: Fri, 02 Sep 2016 22:38:00 -0000 [thread overview]
Message-ID: <CACoZoo3Wi3zs6WC3sDX3BvWWkipZFZ5U_UUBxehhRuZuKnxqXA@mail.gmail.com> (raw)
In-Reply-To: <CAMZ6u3uQHxzrmkNjzZz9R-O8isDs-aPx6pBNoWg4CT_jzFnjCA@mail.gmail.com>
On Fri, Sep 2, 2016 at 5:43 PM, Felipe Vieira wrote:
> no my vimrc. From http://vimdoc.sourceforge.net/htmldoc/map.html:
>
> *<Nop>*
> A easier way to get a mapping that doesn't produce anything, is to use "<Nop>".
>
> Anyways this is not the expected behavior. Is there some complexity
> here that I'm not capturing? In theory I'm disabling the <esc> key and
> that's all. Why is it interfering with m arrow keys and the del key?
If I recall correctly, some keys, including the arrows and DEL, are
actually a very fast combination of other keys, and if you could type
fast enough, you could do the same thing by hitting the corresponding
key sequence. This would also result in effectively disabling all
keys that depend on ESC being the first character of a sequence if you
disable ESC.
Might I ask why you would want to disable ESC in vi?
-- Erik
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-09-02 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 21:43 Felipe Vieira
2016-09-02 22:38 ` Erik Soderquist [this message]
2016-09-02 23:12 ` Gary Johnson
-- strict thread matches above, loose matches on Subject: below --
2016-09-04 15:19 Felipe M. Vieira
2016-09-04 20:48 ` Brian Inglis
2016-09-02 15:04 Felipe Vieira
2016-09-02 16:21 ` Gary Johnson
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=CACoZoo3Wi3zs6WC3sDX3BvWWkipZFZ5U_UUBxehhRuZuKnxqXA@mail.gmail.com \
--to=eriksoderquist@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).