From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: How completions work, do they require fpath?
Date: Wed, 27 Jan 2016 08:59:25 +0100 [thread overview]
Message-ID: <CAKc7PVBcpYc4JjzWfuiqb=wjeQxtGF=vMDgxT7QTdLR2mPcJag@mail.gmail.com> (raw)
In-Reply-To: <160126232017.ZM3789@torch.brasslantern.com>
On 27 January 2016 at 08:20, Bart Schaefer <schaefer@brasslantern.com> wrote:
> No, it doesn't contradict the manual. The check for a directory named
> "Base" is to distinguish "configure --enable-function-subdirs" from the
> default configuration which is to avoid creating subdirectories. If
> the "Base" directory is present it's expected to contain all the
> files from Completion/Base/ in the source tree, and although the
> explicit check is not done the directories AIX/, BSD/, Cygwin/, etc.
> are also expected to be found within $_compdir in that case.
So using _compdir would be a hack, and also, someone can utilize
_compdir for what's it's intended, and overwriting _compdir would
broke their setup.
> This is NOT an indication that you can co-opt these directories for
> plugins, nor is it "safe" to run compinit more than once with a new
> value of $_compdir -- I'm fairly sure you will mangle, or misuse, or
> both, the ~/.zcompdump file if you do so.
So it seems that fpath is needed. I saw Peter's email (workers/12379)
suggesting that work has been done to make fpath the choice for
providing new completions. I wanted to have fpath "clean", and I guess
I can still have it like this: create ~/.zplugin/completions, add it
to fpath, simlink any plugin's "_*" files there. But this will broke
if a completion uses autoload of some functions from plugin's
directory. A very rare case however, I guess.
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-27 7:59 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 [this message]
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
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='CAKc7PVBcpYc4JjzWfuiqb=wjeQxtGF=vMDgxT7QTdLR2mPcJag@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=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).