From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Proof of concept mainstream plugin manager
Date: Sat, 23 Jan 2016 11:20:04 -0800 [thread overview]
Message-ID: <160123112004.ZM14739@torch.brasslantern.com> (raw)
In-Reply-To: <160123093602.ZM14454@torch.brasslantern.com>
On Jan 23, 9:36am, Bart Schaefer wrote:
}
} A less pleasing approach to the whole thing is to use "autoload +X"
Another possibly is this, though it still doesn't address all potential
issues with overly-clever uses of "trap":
shadow-autoload() {
local -a opts
local func
# zparseotps doesn't handle the "+" form, sigh;
# here as placeholder for something more thorough
zparseopts -a opts -D ${(s::):-TUXkmtzw}
if (( $opts[(I)-X] )); then
print -u2 "builtin autoload required for -X"
return 1
fi
if (( $opts[(I)-w] )); then
builtin autoload $opts "$@"
return
fi
for func; do
eval "function $func {
unfunction $func
local FPATH=${(q)PLUGIN_DIR}"'":${FPATH}"'"
autoload $opts $func
$func
}"
done
}
This seems to fix the problems with your "aload" test case. Some old
versions of zsh may have problems with a function that unfunctions
itself, but they're probably old enough not to matter.
next prev parent reply other threads:[~2016-01-23 19:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 19:44 Sebastian Gniazdowski
2016-01-23 1:37 ` Bart Schaefer
2016-01-23 9:03 ` Sebastian Gniazdowski
2016-01-23 15:54 ` Sebastian Gniazdowski
2016-01-23 16:00 ` Sebastian Gniazdowski
2016-01-23 16:09 ` Sebastian Gniazdowski
2016-01-23 16:26 ` Sebastian Gniazdowski
2016-01-23 17:36 ` Bart Schaefer
2016-01-23 19:20 ` Bart Schaefer [this message]
2016-01-23 20:00 ` Bart Schaefer
2016-01-24 10:51 ` Sebastian Gniazdowski
2016-01-24 14:59 ` Sebastian Gniazdowski
2016-01-24 19:06 ` Sebastian Gniazdowski
2016-01-24 20:45 ` Bart Schaefer
2016-06-04 11:36 ` Sebastian Gniazdowski
2016-06-04 17:02 ` Bart Schaefer
2016-01-26 22:50 ` Daniel Shahaf
2016-01-27 7:47 ` Sebastian Gniazdowski
2016-01-26 22:50 ` Daniel Shahaf
2016-01-27 4:34 ` Bart Schaefer
2016-01-27 7:34 ` Sebastian Gniazdowski
2016-01-28 6:38 ` Bart Schaefer
2016-01-28 7:13 ` Sebastian Gniazdowski
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=160123112004.ZM14739@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).