From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@zsh.org
Subject: plugin conventions (Re: off topic)
Date: Wed, 14 Dec 2016 13:40:38 +0100 [thread overview]
Message-ID: <23680.1481719238@hydra.kiddle.eu> (raw)
In-Reply-To: <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
> compinit.
default_zstyle() doesn't prevent it altering an existing user's setup so
unconditional inclusion might be a problem.
Oliver
next prev parent reply other threads:[~2016-12-14 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161209122958.GD19559@256bit.org>
[not found] ` <57127.1481294647@hydra.kiddle.eu>
[not found] ` <584AC8AC.9050406@eastlink.ca>
[not found] ` <62522.1481300922@hydra.kiddle.eu>
[not found] ` <584AEDBF.2050402__19991.0537027337$1481307418$gmane$org@eastlink.ca>
[not found] ` <20161209192406.GA27532@fujitsu.shahaf.local2>
2016-12-11 18:06 ` off topic Peter Stephenson
[not found] ` <584AEDBF.2050402@eastlink.ca>
[not found] ` <161209165454.ZM9226@torch.brasslantern.com>
[not found] ` <95362.1481338226__15466.9970310808$1481338718$gmane$org@hydra.kiddle.eu>
[not found] ` <20161211043221.GA11489@fujitsu.shahaf.local2>
2016-12-11 9:29 ` Plugin conventions (was zsh-users Re: off topic) Bart Schaefer
[not found] ` <95362.1481338226@hydra.kiddle.eu>
[not found] ` <161209191323.ZM9548@torch.brasslantern.com>
2016-12-14 12:40 ` Oliver Kiddle [this message]
2016-12-14 23:51 ` plugin conventions (Re: " Bart Schaefer
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=23680.1481719238@hydra.kiddle.eu \
--to=okiddle@yahoo.co.uk \
--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).