From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: compinit dumps too many files for autoloading
Date: Mon, 04 Oct 2004 12:36:59 +0100 [thread overview]
Message-ID: <200410041137.i94Bb2AD029213@news01.csr.com> (raw)
If I am using a complicate completion such as _perforce which defines
its own functions, then run compinit again, all those functions are
marked for autoloading in .zcompdump. This is problematic because the
functions in question are tested thus in _perforce (_cvs works
similarly):
(( $+functions[_perforce_filetypes] )) ||
_perforce_filetypes() {
...
}
When _perforce is loaded, the test sees that the function is already
marked for autoloading and doesn't define it.
It's not very serious since compinit isn't usually run again. I'm not
sure what the fix is. However, it's not clear to me compinit should be
marking files for autoload unless it found them by searching $fpath.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
next reply other threads:[~2004-10-04 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 11:36 Peter Stephenson [this message]
2004-10-04 16:10 ` Bart Schaefer
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=200410041137.i94Bb2AD029213@news01.csr.com \
--to=pws@csr.com \
--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).