From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Proof of concept mainstream plugin manager
Date: Wed, 27 Jan 2016 08:34:12 +0100 [thread overview]
Message-ID: <CAKc7PVB+wqm2t83obgqop3xAyXtiBSw+z_yVkhOZcFTvHzwxAQ@mail.gmail.com> (raw)
In-Reply-To: <160126203458.ZM2800@torch.brasslantern.com>
On 27 January 2016 at 05:34, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 26, 10:50pm, Daniel Shahaf wrote:
> } Subject: Re: Proof of concept mainstream plugin manager
> }
> } Bart Schaefer wrote on Sat, Jan 23, 2016 at 12:00:55 -0800:
> } > eval "function $func {
> } > _reload_and_run ${(q)PLUGIN_DIR} ${(qq)opts} $func "'"$@"
> } > }'
> }
> } Perhaps change $func to ${(q)func}.
>
> Sebastian has already changed that whole thing to be
>
> functions[$func]="_reload_and_run ${(q)PLUGIN_DIR} $opts $func "'"$@"
I commited your eval way to recognize it in battle (Polish idiom,
wonder if it works in English). Without quoting in ${(qq)opts}, what
you recommended earlier, I get list of all defined functions and their
bodies when shell starts (code visible in 27 sec). I tried this before
but didn't want to bother you because it's hard to express what's
happening, thus the video:
https://asciinema.org/a/eellh7umed2z45685tlhqgdqp
However, suddenly the glitch between ncd and zsh-cdr is gone. Don't
know what's happening, it was there yesterday. I guess it will be
back.
> which yes, is going to do strange things if $func contains spaces.
>
> On the other hand, the whole plugin would already be broken if $func
> contains spaces. I'd rather not "fix" it in an unpredictable way.
What do you mean? Shouldn't I do quoting, i.e. ${(q)func} ?
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-27 7:34 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
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 [this message]
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=CAKc7PVB+wqm2t83obgqop3xAyXtiBSw+z_yVkhOZcFTvHzwxAQ@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=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).