Zsh Mailing List Archive
Messages sorted by:
plugin conventions (Re: off topic)
- X-seq: zsh-workers 40182
- From: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: plugin conventions (Re: off topic)
- Date: Wed, 14 Dec 2016 13:40:38 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1481719239; bh=aunjO0hcBDe4RavFhW9l+GE2Kygq0xnneEqKwVWGYFU=; h=In-reply-to:From:References:To:Subject:Date:From:Subject; b=NXqtQvFXMeoVNTua9gKbMXw+KNjzzEO8vhvj5CCeWOE1oplZv9OaAGjk5Q8uJMn7vtv7WubCM4l3MRXLu+ICztOqSmPG/NNTUA04DPXKQUYKuFU1+fppe68KZkhlGJvlwEEJ/grM9v8pvRfIInlSxv7EU5E1AHi/g9XbKIrrMYvNOnzYidzMa4eiud/cZaj9sbS5N1zPnE1u7x8k3wYOafWHQwiiSy4dZafJes6Eh1HzRCrn7YgwAwlG5+KqG8oH5nDf8+Yy6fSpe9LUERIm1N+QVU+Xi6gY9eI2cWtvLJcf3no/znIVNQ+Wkcwy6JvArDAUetC7+CbnwdfODi3gKQ==
- In-reply-to: <161209191323.ZM9548@torch.brasslantern.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20161209122958.GD19559@256bit.org> <firstname.lastname@example.org> <584AC8AC.email@example.com> <firstname.lastname@example.org> <584AEDBF.email@example.com> <161209165454.ZM9226@torch.brasslantern.com> <firstname.lastname@example.org> <161209191323.ZM9548@torch.brasslantern.com>
On 9 Dec, Bart wrote:
> On Dec 10, 3:50am, Oliver Kiddle wrote:
> } Rather than a source-able file, would it perhaps make sense to embrace
> } the concept of plugins.
> If we're going that route, the plugin manager that Sebastian has been
> asking us for advice about for the last several months might be an
> interesting idea.
It's certainly an option to take an existing plugin manager and without
having looked into any of them, I would tend to assume that Sebastian's
is the best. It is also clearly very feature rich.
I used the wording "rudimentary plugin manager" because what I had
in mind foremost is standardising the conventions. A basic reference
implementation helps with documenting that and determining what issues
there might be. But perhaps that's already known. For example, I seem
to remember something about the various frameworks causing compinit to
be run multiple times. A pure plugin manager has no business running
compinit even once but if there is a fundamental reason such as needing
to do something only after compinit has run then perhaps we could add a
hook in to compinit. Or was a good solution found for zplugin?
> Although the idea with this particular file was simply to fold it in to
default_zstyle() doesn't prevent it altering an existing user's setup so
unconditional inclusion might be a problem.
Messages sorted by: