From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Wordcode bug with $functions
Date: Tue, 01 Feb 2000 20:53:26 +0000 [thread overview]
Message-ID: <E12FkFl-0002L6-00.2000-02-01-20-50-25@mail1.svr.pol.co.uk> (raw)
I'm getting a segmentation fault with `print $functions', even patched up
to date (supposedly). I presume this is a new wordcode feature. This is
reproducible with my addpath function by doing `which addpath'. I narrowed
it down: actually, this form doesn't give a crash, but it does show more
clearly what's going wrong.
By the way, I found this by doing `set' on its own. This dumps out the
whole of every function when zsh/parameter is loaded. Yuck.
% fn() {
a() { true; }
b() { true; }
}
% which fn
unknown word code in gettext2()
fn () {
a () {
true
}
}
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
next reply other threads:[~2000-02-01 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-01 20:53 Peter Stephenson [this message]
2000-02-02 8:45 Sven Wischnowsky
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=E12FkFl-0002L6-00.2000-02-01-20-50-25@mail1.svr.pol.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-workers@sunsite.auc.dk \
/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).