From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: Compsys and KSH_AUTOLOAD
Date: Mon, 12 Apr 2004 23:43:07 +0200 [thread overview]
Message-ID: <3571.1081806187@athlon> (raw)
In-Reply-To: <040412085942.ZM19035@candle.brasslantern.com>
Bart wrote:
> Matthias has since written back to me again and says he's having all sorts
> of problems with zcompile'd functions even after starting from scratch and
I've had problems with it in the past so it probably needs more
investigation.
> I don't specifically mean "does the above workaround deserve a FAQ entry"
> but rather "does using compsys with kshautoload deserve a FAQ entry",
> whatever the best A to the Q turns out to be.
It probably does deserve an FAQ entry. The minimum possible A to the Q
will be to use -z when using autoload for compinit. With that we either
need an FAQ or to suggest the -z everywhere we show the autoload -U
compinit.
> The autoload method used isn't stored anywhere in the function structure.
> Only the fact that the function is not yet defined is stored, and then zsh
> applies whatever autoload setting is in effect globally at the time that
> the function is loaded.
Presumably it also stores whether the function was autoloaded with the
-U option. Looks like there is a PM_UNALIASED flag. Maybe we can just
add PM_ZSHSTORED and PM_KSHSTORED flags.
> I suppose we could modify the storage and the code that does autoloading
> [as opposed to modifying only bin_autoload()]; I forget why I didn't do
> so at the time -- probably because it was a significantly larger change.
It just needs a bit of investigation then to see if there was a more
fundamental reason. I was wondering if there was some clash with
typeset options (autoload being a variant of it). Hopefully not.
Oliver
next prev parent reply other threads:[~2004-04-12 21:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 17:44 Bart Schaefer
2004-04-12 14:00 ` Oliver Kiddle
2004-04-12 15:59 ` Bart Schaefer
2004-04-12 21:43 ` Oliver Kiddle [this message]
2004-04-13 5:32 ` While we're on the subject of zcompile Bart Schaefer
2004-04-17 21:08 ` Oliver Kiddle
2004-04-13 5:38 ` Compsys and KSH_AUTOLOAD Bart Schaefer
2004-04-13 15:29 ` PATCH: " Oliver Kiddle
2004-04-13 17:51 ` Bart Schaefer
2004-04-16 16:49 ` Oliver Kiddle
2004-04-16 17:25 ` Bart Schaefer
2004-04-18 13:46 ` Oliver Kiddle
2004-04-16 17:30 ` Bart Schaefer
2004-04-17 19:51 ` Oliver Kiddle
2004-04-19 0:14 ` Bart Schaefer
2004-04-19 10:18 ` Oliver Kiddle
2004-04-20 4:11 ` Bart Schaefer
2004-04-20 10:08 ` Oliver Kiddle
2004-04-14 5:04 ` Bart Schaefer
2004-04-14 19:55 ` Peter Stephenson
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=3571.1081806187@athlon \
--to=okiddle@yahoo.co.uk \
--cc=zsh-workers@sunsite.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).