From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: A method to not leak unneeded functions
Date: Mon, 30 Sep 2019 00:25:12 +0200 [thread overview]
Message-ID: <CAKc7PVAnQgDupk_-h85r-FtWna2KCQ+N0VS0zLynKFSydwU=MQ@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVBiatCfaG5xupix8d8+VH_ScZJRRRJemUuND12Zk0TJuw@mail.gmail.com>
PS. The block of code should be added at the beginning of the autoload
file, after possible emulate -L zsh, or at least after `setopt
localtraps' (which is being done by the emulate builtin). After this
the setup is complete and the functions will get automatically unset.
On Mon, 30 Sep 2019 at 00:22, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> Hello,
> it's often the case when one declares sub-functions inside an autoload
> function. The function will leak into the shell and also get redefined
> on the next run of the main function. Here's a method to prevent this
> from happening:
>
> local -a entry_funs
> entry_funs=( ${(k)functions} )
> trap "unset -f \"\${(k)functions[@]:#(${(j:|:)${(q@)entry_funs}})}\"
> &>/dev/null" EXIT
> trap "unset -f \"\${(k)functions[@]:#(${(j:|:)${(q@)entry_funs}})}\"
> &>/dev/null; return 1" INT
>
> It will unset any newly detected functions at the moment of leaving of
> the main function.
> --
> Sebastian Gniazdowski
> News: https://twitter.com/ZdharmaI
> IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
> Blog: http://zdharma.org
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2019-09-29 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 22:22 Sebastian Gniazdowski
2019-09-29 22:25 ` Sebastian Gniazdowski [this message]
2019-10-03 23:18 ` Sebastian Gniazdowski
2019-10-03 23:25 ` 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='CAKc7PVAnQgDupk_-h85r-FtWna2KCQ+N0VS0zLynKFSydwU=MQ@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=zsh-users@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).