Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <20160125103653.GB6416@pjcj.net>
References: <CAKc7PVB0NAc5ZHV5FpnHD4B4YU1XNXbr1TkWgxOwe3x8k48DBA@mail.gmail.com>
 <20160125103653.GB6416@pjcj.net>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Mon, 25 Jan 2016 12:05:39 +0100
Message-ID: <CAKc7PVDvimtKkC+w7ocLExmtc5skjTejbfr9JKa9-WHzi9sf7w@mail.gmail.com>
Subject: Re: ZPlugin
To: Paul Johnson <paul@pjcj.net>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On 25 January 2016 at 11:36, Paul Johnson <paul@pjcj.net> wrote:
> Just an observation from the peanut gallery: as I understand it you have
> created a more elegant solution to the core of a plugin system.  Would
> it, therefore, make any sense, rather than building your own plugin
> system from scratch, to fit your solution into an existing plugin
> system, such as Zplug?

I'm using existing "plugin system". Tested 20 plugins and all loaded
correctly. I think there is a problem with perceiving the existing
tools as an sophisticated advanced technology. In reality, it's
fpath+= to the plugin's dir and not much more. This is innovative, but
for sure it isn't a tragedy to just ignore what already exists. Zplug
has some additional functionality that I want to recognize today,
maybe that's a different case.

> Are there sound technical reasons not to do so, or are you enjoying
> building your own and want to continue with it?

Well ZPlugin is designed from scratch to reveal as much as possible
from plugins internals at time of loading it. It's hard to add this to
existing projects.

Best regards,
Sebastian Gniazdowski