From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Surprising effect of fun() { local FPATH=...; autoload -X }, and a bug
Date: Thu, 29 Sep 2016 00:10:04 -0700 [thread overview]
Message-ID: <160929001004.ZM27686@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVCXq6jQe2gF-Hb4UFBx7UXxRE=3_8Z2Oyq-H6d0LoNLAA@mail.gmail.com>
On Sep 27, 12:07am, Sebastian Gniazdowski wrote:
}
} eval "function $func {
} local FPATH="$PLUGIN_DIR":"${FPATH}"
} builtin autoload -X ${opts[*]}
} }"
}
} What I astonishingly realized today is that functions autoloaded this
} way can further use autoload builtin purely normally. FPATH visible
} from the specially-autoloaded function is modified, has the required
} added component, and builtin autoload works as expected (even with
} <5.1 Zsh, it has a more specific manual autoload stub).
This will be the case as long as the autoload command AND the first
run of the normally-autoloaded function BOTH happen during the FIRST
run of the "specially-loaded" function.
E.g. suppose we have this silly example:
--8<-- file "outer" --8<--
if (( $+functions[inner2] )); then
inner2
else
autoload inner1 inner2
inner1
fi
-->8-- file "outer" -->8--
and we send func=outer through your eval above. When "outer" is first
run, the call stack will look like
outer # scope of local FPATH is here
autoload -X
outer # "normal autoloads" are here
inner1 # modified FPATH is still in scope
In this case inner1 will load with the modified FPATH. On the second
and subsequent runs of "outer", the call stack will look like:
outer # no FPATH declared
inner2 # no modified FPATH in scope
thus inner2 will load from the normal fpath. It's the fpath at time of
function call that matters, not the fpath at time of autoload command.
next prev parent reply other threads:[~2016-09-29 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 22:07 Sebastian Gniazdowski
2016-09-27 7:05 ` Daniel Shahaf
2016-09-27 7:54 ` Sebastian Gniazdowski
2016-09-29 7:10 ` Bart Schaefer [this message]
2016-09-29 9:42 ` Sebastian Gniazdowski
2016-09-29 10:05 ` Sebastian Gniazdowski
2016-09-29 13:58 ` Sebastian Gniazdowski
2016-09-29 21:50 ` Bart Schaefer
2016-09-30 6:03 ` Sebastian Gniazdowski
2016-09-30 15:31 ` Bart Schaefer
2016-09-30 17:41 ` Sebastian Gniazdowski
2016-09-30 17:53 ` Sebastian Gniazdowski
2016-09-30 20:13 ` Bart Schaefer
2016-09-30 6:49 ` Daniel Shahaf
2016-09-30 18:16 ` 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=160929001004.ZM27686@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).