From: Filipe Silva <filipe.silva@gmail.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-users@zsh.org
Subject: Re: [vi-mode] widgets for case manipulation: `gU` and `U` in visual mode
Date: Thu, 23 Jun 2016 01:30:22 -0300 [thread overview]
Message-ID: <CAEwkUWPjjxy6=J8-zwE3n-U6c35oAgA_vdg=GqJ+aSwFkc07cw@mail.gmail.com> (raw)
In-Reply-To: <27903.1466634569@thecus.kiddle.eu>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Oliver,
thanks for pointing out the issue.
Having an ESCKEYTIMEOUT would be awesome. Setting KEYTIMEOUT to anything
above 5 is quite noticeable and laggy when I want to return to normal mode.
KEYTIMEOUT=1 is snappy, but then I lose out on the surround widget and
whatnot because I can't type `ys` fast enough.
On Wed, Jun 22, 2016 at 7:29 PM, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> Filipe Silva wrote:
> >
> > "If this is the problem, it has also been fixed in newer versions by
> > making it continue waiting for further keys if the keys typed so far,
>
> > What recent versions would those be? since 5.2?
>
> Actually, the change was made in December 2014 - before 5.0.8. However,
> looking at your setup, it seems that you have in effect the following:
> cutbuffer() {
> zle .$WIDGET
> echo $CUTBUFFER | pbcopy
> }
> zle -N vi-yank cutbuffer
>
> The custom cutbuffer widget is not marked as being a vi operator so gets
> invoked as soon as you press y. Currently, I can't think of an easy fix
> for this. In the past, we considered allowing flags to be set on custom
> widgets and I also pondered having a separate ESCKEYTIMEOUT variable.
>
> As an aside, you might want to guard against $CUTBUFFER starting with a
> - or containing \ escapes. Consider using printf or print -r --. Or
> perhaps pbcopy <<<"$CUTBUFFER"
>
> Oliver
>
next prev parent reply other threads:[~2016-06-23 4:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 18:51 Filipe Silva
2016-06-21 23:10 ` Oliver Kiddle
2016-06-22 6:42 ` Bart Schaefer
2016-06-22 13:19 ` Filipe Silva
2016-06-22 13:23 ` Filipe Silva
2016-06-22 15:09 ` Oliver Kiddle
2016-06-22 15:25 ` Filipe Silva
2016-06-22 15:28 ` Filipe Silva
2016-06-22 22:29 ` Oliver Kiddle
2016-06-23 4:30 ` Filipe Silva [this message]
2016-06-23 5:28 ` Bart Schaefer
2016-06-23 22:37 ` Bart Schaefer
2016-06-22 19:10 ` Filipe Silva
2016-06-22 20:11 ` Oliver Kiddle
2016-06-22 20:19 ` Bart Schaefer
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='CAEwkUWPjjxy6=J8-zwE3n-U6c35oAgA_vdg=GqJ+aSwFkc07cw@mail.gmail.com' \
--to=filipe.silva@gmail.com \
--cc=okiddle@yahoo.co.uk \
--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).