From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Adam Spiers <adam@spiers.net>, zsh-workers@sunsite.auc.dk
Subject: Re: missing -o kshautoload checks
Date: Tue, 1 Aug 2000 07:12:36 +0000 [thread overview]
Message-ID: <1000801071236.ZM27240@candle.brasslantern.com> (raw)
In-Reply-To: <20000731231407.A32629@thelonious.new.ox.ac.uk>
On Jul 31, 11:14pm, Adam Spiers wrote:
}
} A recursive grep for '_[a-z_]* "$@"' in the Completion directory
} reveals that there are quite a few of these [[ -o kshautoload ]]
} checks missing. I'm a bit short on time right now; any kind soul care
} to add them in?
I think there was at least a semi-conscious decision to stop including
those lines. Chapter "Completion System" section "Initialization" heading
"Autoloaded files" explains:
Note also that the functions for the completion system assume that the
KSH_AUTOLOAD option is not set and cannot be loaded when it is set. To
avoid having to unset KSH_AUTOLOAD, you can instead use one or more zwc
file which have been created with the command zcompile -z to load
the functions for the completion system; see *Note Shell Builtin
Commands::. This forces the functions to be autoloaded the way zsh
normally loads functions.
I haven't actually tried it, but I'm pretty sure that if you `zcompile -z'
a file that ends with `[[ -o kshautoload ]] && $0 "$@"', and you have
kshautoload set, you'll end up executing the function *twice* the first
time it's autoloaded. So really we should be *removing* all the checks
for kshautoload, not adding more of them.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-08-01 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 10:29 PATCH: mysql completions Sven Wischnowsky
2000-07-31 22:14 ` missing -o kshautoload checks Adam Spiers
2000-08-01 7:12 ` 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=1000801071236.ZM27240@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=adam@spiers.net \
--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).