From: Wayne Davison <wayned@users.sourceforge.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Overriding a yank* widget in zle
Date: Fri, 31 Dec 2010 15:23:19 -0800 [thread overview]
Message-ID: <AANLkTinNwsFcoMU=iuSdcS69k3=M9XxTxjHfjvR2vKW3@mail.gmail.com> (raw)
In-Reply-To: <101231002820.ZM7583@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Fri, Dec 31, 2010 at 12:28 AM, Bart Schaefer
<schaefer@brasslantern.com>wrote:
> Perhaps a general solution would be that for *any* widget, not just a
> completion one, it should be possible to name a "prototype" widget whose
> behavior the new widget is intended to simulate or replace.
>
That seems like a great solution to me.
The only other solution to this that I've thought of would be to follow the
> example of the auto-suffix-remove and auto-suffix-retain widgets, that is,
> have a special widget whose only effect is to have the side-effect of
> enabling yank-pop on the next interaction: yank-pop-enable perhaps (is
> yank-pop-disable ever needed?).
>
Something like that would work if done right. I tried something along those
lines (it was named "yank-noop"), but hadn't worked out the right bits to
make the flags stick around long enough before I changed direction. I like
the prototype idiom best, though.
..wayne..
next prev parent reply other threads:[~2010-12-31 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 21:59 Wayne Davison
2010-12-31 6:39 ` Wayne Davison
2010-12-31 8:28 ` Bart Schaefer
2010-12-31 23:23 ` Wayne Davison [this message]
2015-08-31 7:54 ` PATCH: Implement zle -P Mikael Magnusson
2015-08-31 7:56 ` Mikael Magnusson
2015-08-31 9:55 ` PATCH: Set completion function flags correctly for " Mikael Magnusson
2015-08-31 10:17 ` Mikael Magnusson
2015-08-31 17:11 ` PATCH: Implement " Peter Stephenson
2015-09-01 6:23 ` Bart Schaefer
2015-09-01 6:50 ` Mikael Magnusson
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='AANLkTinNwsFcoMU=iuSdcS69k3=M9XxTxjHfjvR2vKW3@mail.gmail.com' \
--to=wayned@users.sourceforge.net \
--cc=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).