Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Vimode problem (key press dropping)
- X-seq: zsh-users 20359
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Vimode problem (key press dropping)
- Date: Wed, 29 Jul 2015 17:35:14 +0200
- Cc: Zsh Users <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e52b4OzpJmtRxRYG4tpQDS4Y7mGAx+U6ehfMODJdpVw=; b=HR73gaRvWLzK5x5D62eEUoPXKm7QvtveDvKEbdZQRwoCUNi6ClGMd/nCoDK5m4hcv4 60OwPuhlkq4gE8Z+JY+39ObBt1EZ+LmS/YDJJiiA9Gqb8geO8bcfaIRmdT7Qxa5Rmfl5 kvBsje0r05D1k7jDV05TPlDOPREs/6pnp6DSBiChzdbdzCnRmiUFAkpcZP5V07BHIZfM s5wCfmJzaqZKZvaZY1QJZwXmIcT0PTcbJpolyLmwza8WmdIoUHMvg+8wPzSWUX5zZryh mxMo5xFW9wyqayhz/VTZDzOEVv1CSFI3HfmbLzXY52tLrVqr0+QCwF/TFTyBVXz2olty DBZw==
- In-reply-to: <150729083027.ZM10252@torch.brasslantern.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <5d9984411ba10dee4321a408e2763317@riseup.net> <9361.1438161965@thecus.kiddle.eu> <CAHYJk3SDG5r0i3+=vRMt_ERVpwmwnf0Y3S2cf60_PpLa2mf7Tg@mail.gmail.com> <150729083027.ZM10252@torch.brasslantern.com>
On Wed, Jul 29, 2015 at 5:30 PM, Bart Schaefer
<schaefer@xxxxxxxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author