zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Off-by-one with select-*-shell-word text object?
Date: Fri, 16 Sep 2016 20:02:05 -0700	[thread overview]
Message-ID: <160916200205.ZM27241@torch.brasslantern.com> (raw)
In-Reply-To: <10734.1474068633@hydra.kiddle.eu>

On Sep 17,  1:30am, Oliver Kiddle wrote:
} Subject: Re: Off-by-one with select-*-shell-word text object?
}
} Bart wrote:
} > It also occurs to me to wonder whether set_bindk = 0 *ever* makes sense
} > for builtin widgets.  Can somebody give me an example of a builtin that
} > would care about the widget name of its user-defined caller?
} 
} I think it matters for the k2 == bindk test in getvirange().

That gets me wondering about the execzlefunc() call in getvirange().
E.g. in vicmd mode, cS changes nothing but leaves me in insert mode.
Probably should be an error to invoke any ZLE_VIOPER widget *other*
than the same one again?  But I digress ...

} zlecallhook sets set_bindk. That doesn't seem entirely useful

Actually it's quite useful, and the recently-added add-zle-hook-widget
function depends on it (to the point that zle-line-pre-redraw was
changed to match).

} run-help, which-command and zap-to-char suffer from the same
} issue as the text object widgets: they use bindk to select their
} behaviour. 
} 
} So any thoughts on this solution?

I'd probably write it as an assignment of setbindk rather than put the
whole expression in the execzlefunc argument, but otherwise this seems
sensible on the face of it.


  reply	other threads:[~2016-09-17  3:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 17:21 Bart Schaefer
2016-09-16 20:47 ` Oliver Kiddle
2016-09-16 21:22   ` Bart Schaefer
2016-09-16 23:30     ` Oliver Kiddle
2016-09-17  3:02       ` Bart Schaefer [this message]
2016-09-17  7:42         ` Daniel Shahaf
2016-09-17 14:29           ` Bart Schaefer
2016-09-19  7:00             ` Daniel Shahaf
2016-09-19 10:01               ` Oliver Kiddle
2016-09-19 15: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=160916200205.ZM27241@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@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).