public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: updated vim broke arrow/delete keys
Date: Sun, 04 Sep 2016 20:48:00 -0000	[thread overview]
Message-ID: <dc4c8aa2-7af8-8f5a-7416-71ceb0b604b7@SystematicSw.ab.ca> (raw)
In-Reply-To: <20160904151924.GA3782@gmail.com>

On 2016-09-04 09:19, Felipe M. Vieira wrote:
> The motive:
> http://learnvimscriptthehardway.stevelosh.com/chapters/10.html

If the title alone does not put you off, it should be a warning,
and the author warns it is not a tutorial, it is one way to learn
how to customize vim, and I would add, should be done in a sandbox:
a separate account from your working account, and only after reading
the whole article from start to finish before trying anything,
as the impact of the changes is nowhere clearly explained, just what
the immediate effect is and whay that is considered desirable by the
author.

> The idea is to force yourself to use a faster escape key.
> the output of that command:
>   timeoutlen=1000
>   ttimeoutlen=-1
> I guess the final answer is the one from Randy Morris:
> https://stackoverflow.com/questions/8488232/how-to-disable-esc-and-cursor-keys-in-vim
> "In conclusion, don't remap escape, I almost guarantee you will have unexpected consequences."
> It feels like <esc> and some other keys are a combination of other keys as Erik
> pointed out.
> I'm going to send an email to the author of vimscript to add a warning or
> something like that.

Send the email to the author of the article Steve Losh, and
suggest his article could be improved by discussing the impact
of his changes, and not just the immediate effect; I suspect
the author of vim and its scripting language Bram Moolenaar
would be unlikely to suggest remapping <esc>!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

  reply	other threads:[~2016-09-04 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 15:19 Felipe M. Vieira
2016-09-04 20:48 ` Brian Inglis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-02 21:43 Felipe Vieira
2016-09-02 22:38 ` Erik Soderquist
2016-09-02 23:12 ` Gary Johnson
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=dc4c8aa2-7af8-8f5a-7416-71ceb0b604b7@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).