zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] add-zle-hook-widget
Date: Thu, 14 Jul 2016 00:45:19 -0700	[thread overview]
Message-ID: <160714004519.ZM23514@torch.brasslantern.com> (raw)
In-Reply-To: <20160705045757.GD11492@tarsus.local2>

On Jul 5,  4:57am, Daniel Shahaf wrote:
}
} Note there are alternatives to specifying detailed partial orders: for
} example, one could hook a single function that invokes a few other ones

This gives me an interesting idea:  The list of hook types is stored
in a zstyle.  So you could theoretically add your own new hook types
to that style, and hey presto, add-zle-hook-widget will let you manage
a hook "array" for your new hook name.

    azhw:zle-new-hook-name() { ... }
    zle -N zle-new-hook-name azhw:zle-new-hook-name
    $(zstyle -L zle-hook types) new-hook-name

    add-zle-hook-widget new-hook-name some-other-widget
    add-zle-hook-widget new-hook-name yet-another-widget

Then you can add all of your hooks to one of the built-in hooks like

    add-zle-hook-widget line-init zle-new-hook-name

Hmm.


      reply	other threads:[~2016-07-14  7:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  1:44 Bart Schaefer
2016-06-13  8:52 ` Daniel Shahaf
2016-06-14 18:10   ` Bart Schaefer
2016-06-14 21:06     ` Bart Schaefer
2016-06-15 23:24     ` Daniel Shahaf
2016-06-17  5:20       ` Bart Schaefer
2016-06-18 23:25         ` Bart Schaefer
2016-06-21  1:41           ` Daniel Shahaf
2016-06-21 22:58             ` Bart Schaefer
2016-06-21  1:41         ` Daniel Shahaf
2016-06-22 20:25           ` Bart Schaefer
2016-07-01  5:11             ` Daniel Shahaf
2016-07-01 20:11           ` Bart Schaefer
2016-07-05  4:57             ` Daniel Shahaf
2016-07-14  7:45               ` Bart Schaefer [this message]

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=160714004519.ZM23514@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).