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: Wed, 22 Jun 2016 16:10:01 -0300 [thread overview]
Message-ID: <CAEwkUWOAvbT4xydtG6EZYRS3tOuur1LZ3tJAx97jR8zgFBjsyw@mail.gmail.com> (raw)
In-Reply-To: <25350.1466608182@thecus.kiddle.eu>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
Oliver, (and for whoever is interested in these widgets)
Just a small update on the fix. the correct condition is as follows (the
other that I've gave you also contains a bug).
if [[ $CURSOR = '0' ]]; then
zle .vi-put-before -n 1
else
zle .vi-put-after -n 1
fi
updated plugin section:
https://github.com/ninrod/nin-vi-mode/blob/master/nin-vi-mode.plugin.zsh#L126-L130
cheers and thanks again.
On Wed, Jun 22, 2016 at 12:09 PM, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> Filipe Silva wrote:
> > for instance, the `ys` chord is not being picked up.
> >
> > supose i have a word: `abcde` and the cursor is in `c`. if I'm in
> > normal mode and type `ys` zle thinks that I've hit `s` and deletes the
> > `c` character and puts me in insert mode.
> >
> > Maybe it's a bug?
>
> I think this occurs if you don't type ys fast enough. What have you got
> $KEYTIMEOUT set to? Try typing the ys especially fast. And perhaps try
> binding ys to something that will be obvious like kill-whole-line to see
> if it is surround that is failing or the key binding.
>
> 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,
> such as y, correspond to a widget, such as vi-yank, that needs to wait
> for a movement. This also allows tricks like
> bindkey -a -s 'cw' 'dwi'
> to work much as the equivalent vi map.
>
> Similarly, I can define
> bindkey -s -a "gUU" "gUgU"
> but because vi-uppercase is not a builtin widget, I need to hit the keys
> fast even in 5.2.
>
> > On Wed, Jun 22, 2016 at 10:19 AM, Filipe Silva <filipe.silva@gmail.com>
> > wrote:
> > > I've fixed the bug including the following condition:
>
> Thanks for that!
>
> Oliver
>
next prev parent reply other threads:[~2016-06-22 19:10 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
2016-06-23 5:28 ` Bart Schaefer
2016-06-23 22:37 ` Bart Schaefer
2016-06-22 19:10 ` Filipe Silva [this message]
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=CAEwkUWOAvbT4xydtG6EZYRS3tOuur1LZ3tJAx97jR8zgFBjsyw@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).