From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Cc: tetsujin@scope-eye.net
Subject: Re: Building a new ZSH module outside the ZSH source tree
Date: Wed, 24 May 2017 14:19:02 -0700 [thread overview]
Message-ID: <170524141902.ZM15541@torch.brasslantern.com> (raw)
In-Reply-To: <45fd7d7b777636cd074be985ca63ccc644ee4b69@webmail.scope-eye.net>
On May 24, 2:57pm, tetsujin@scope-eye.net wrote:
}
} nice programming interface for modules, but I'm not really clear on
} the process for building a module without tying it into the zsh build
} system.
I haven't actually tried the following yet.
--- Forwarded mail from Sebastian Gniazdowski <psprint2@fastmail.com>
X-Seq: 40477
From: Sebastian Gniazdowski <psprint2@fastmail.com>
To: zsh-workers@zsh.org
Subject: Modules can be built outside Zsh; custom version of autoload builtin
Date: Wed, 01 Feb 2017 09:48:51 -0800
Hello
1/ Turned out that it's easy to build Zsh modules away from complete
source. Here is a minimum build setup:
https://github.com/psprint/zplugin/tree/6a4ba014eb167cbc97353f0a59e63f62bd6442bc/zmodules
Tested this on OS X. I can load module built with Zsh 5.3.1 features
even on Apple-provided 5.0.8. It's only that lazy binding will fail, if
I call non-existent (in 5.0.8) function. So, plugin creators can
actually provide binary parts, what I'm intending to do too, in Zplugin.
next prev parent reply other threads:[~2017-05-24 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 18:57 tetsujin
2017-05-24 21:19 ` Bart Schaefer [this message]
2017-05-24 22:41 ` tetsujin
2017-05-25 13:00 ` Sebastian Gniazdowski
2017-05-26 5:54 ` George
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=170524141902.ZM15541@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=tetsujin@scope-eye.net \
--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).