zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: How completions work, do they require fpath?
Date: Thu, 28 Jan 2016 11:29:41 -0800	[thread overview]
Message-ID: <160128112941.ZM20292@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVCaf3qbwq_5RS-EwqHnhC+fSMPn+c4bJMuib9qYnyhcGA@mail.gmail.com>

On Jan 28,  8:37am, Sebastian Gniazdowski wrote:
}
} One thing emerged - I was expecting that empty say "_cp" will just be
} ignored, because of lack of #compdef, however it isn't - it blocks
} other "_cp" files from loading.

That doesn't have anything to do with compinit, that's just the way
autoloading always works.  Compinit marks the names to be autoloaded,
but it doesn't control where they come from when autoloading finally
happens.  This was bashed out in agonizing detail with Ray Andrews
back in September.

The reload-and-run trick could circumvent this, that is, if your
autoload shadow were defined before compinit runs, then all of the
functions it touches would load from the place they were found at
compinit time rather than at execution time.

But it would make compinit a bit slower and use a bit more memory.


      parent reply	other threads:[~2016-01-28 19:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 17:18 Sebastian Gniazdowski
2016-01-26 19:51 ` Sebastian Gniazdowski
2016-01-27  7:20   ` Bart Schaefer
2016-01-27  7:59     ` Sebastian Gniazdowski
2016-01-28  7:11       ` Bart Schaefer
2016-01-28  7:37         ` Sebastian Gniazdowski
2016-01-28  7:39           ` Sebastian Gniazdowski
2016-01-28 23:23             ` Bart Schaefer
2016-01-29  8:02               ` Sebastian Gniazdowski
2016-01-31 19:26                 ` Bart Schaefer
2016-01-28 19:29           ` 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=160128112941.ZM20292@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).