Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160714004519.ZM23514@torch.brasslantern.com>
Date: Thu, 14 Jul 2016 00:45:19 -0700
In-Reply-To: <20160705045757.GD11492@tarsus.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
        "Re: [PATCH] add-zle-hook-widget" (Jul  5,  4:57am)
References: <160612184453.ZM11316@torch.brasslantern.com> 
	<20160613085219.GA23148@tarsus.local2> 
	<160614111054.ZM17893@torch.brasslantern.com> 
	<20160615232447.GA29225@tarsus.local2> 
	<160616222055.ZM27034@torch.brasslantern.com> 
	<20160621014130.GA17100@tarsus.local2> 
	<160701131158.ZM9615@torch.brasslantern.com> 
	<20160705045757.GD11492@tarsus.local2>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] add-zle-hook-widget
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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.