From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Vimode problem (key press dropping)
Date: Wed, 29 Jul 2015 17:35:14 +0200 [thread overview]
Message-ID: <CAHYJk3SJziK+U9sPE9xaPYjwvPw8L7+x6fnYDoVAzwo+XYm6hw@mail.gmail.com> (raw)
In-Reply-To: <150729083027.ZM10252@torch.brasslantern.com>
On Wed, Jul 29, 2015 at 5:30 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Jul 29, 2:35pm, Mikael Magnusson wrote:
> }
> } I always felt like how it should work if we get the string "abc", is
> } first abc is looked up and we find it isn't bound to anything, the a
> } gets treated as a separate input string, then we look up bc instead,
> } etc.
>
> The problem with that is that if you have an unbound function key on
> your keyboard, striking it will cause unpredictable effects when the
> leading ESC is ignored and the rest of the sequence begins to be
> interpreted as individual characters.
>
> } What we do now is just discard the whole string as "undefined-key".
>
> Which is correct if the whole sequence came from a single keystroke;
> the real difficulty is determining whether that happened.
Well, what almost always happens is we eat the ^[[1 part and insert
the ~ literally, which is confusing. If we literally inserted the
whole ^[[1~ string, it would be more obvious for a user what they had
to put in their keybind commands. "You can run cat and press the key
to see what it sends" "oh, okay".
--
Mikael Magnusson
next prev parent reply other threads:[~2015-07-29 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 5:17 alx741
2015-07-29 9:26 ` Oliver Kiddle
2015-07-29 12:35 ` Mikael Magnusson
2015-07-29 15:30 ` Bart Schaefer
2015-07-29 15:35 ` Mikael Magnusson [this message]
2015-07-29 15:51 ` Bart Schaefer
2015-07-29 16:31 ` Mikael Magnusson
2015-07-29 16:45 ` Oliver Kiddle
2015-07-29 17:49 ` Bart Schaefer
2015-07-29 17:53 ` Bart Schaefer
2015-07-29 18:32 ` alx741
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=CAHYJk3SJziK+U9sPE9xaPYjwvPw8L7+x6fnYDoVAzwo+XYm6hw@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).