From: Bart Schaefer <schaefer@brasslantern.com>
To: Sebastian Gniazdowski <psprint@zdharma.org>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Strange or interesting zcompile behavior, for in-loop func defs
Date: Mon, 17 Jul 2017 23:10:41 -0700 [thread overview]
Message-ID: <CAH+w=7ZHk7pZnQm=XPutGJzARuQBfchme9zxBm+8QSPz4tJAdg@mail.gmail.com> (raw)
In-Reply-To: <etPan.596cc0c2.33e30cbe.6b4@zdharma.org>
On Mon, Jul 17, 2017 at 6:50 AM, Sebastian Gniazdowski
<psprint@zdharma.org> wrote:
>
> Have dump for: _zsh_highlight_widget_zle-isearch-update, file: /Users/sgniazdowski/.zplugin/lexicon.zwc
I'm fairly sure the dump structure is being found from the Eprog for
the _zsh_highlight_bind_widgets function, which contains the loop in
question, and is not actually the dump of the
_zsh_highlight_widget_zle-isearch-update function.
prev parent reply other threads:[~2017-07-18 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 13:50 Sebastian Gniazdowski
2017-07-18 6:10 ` Bart Schaefer [this message]
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='CAH+w=7ZHk7pZnQm=XPutGJzARuQBfchme9zxBm+8QSPz4tJAdg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=psprint@zdharma.org \
--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).