From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: How completions work, do they require fpath?
Date: Tue, 26 Jan 2016 20:51:14 +0100 [thread overview]
Message-ID: <CAKc7PVCqw_Z+RnjzwEtoRVLSE1A9JSyVQYpg1E=6u5em5qDdkg@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVCMPay34XS9up_CP-iZ79xPt2sZw35ngPBZZGN=_SRX_Q@mail.gmail.com>
I've found following line in compaudit command:
if [[ $#_i_files -lt 20 || $_compdir = */Base || -d $_compdir/Base ]]; then
So this suggests that if there is Base sub directory in $_compdir, it
will be used by completion. Tested this and that's true. Quite
contradict to manual which says:
"For incomplete installations, if compinit does not find enough
files eginning with an underscore (fewer than twenty) in the search
path, it will try to find more by adding the directory _compdir to
the search path."
Anyway, it seems that I will be able to add completions as follows: a)
create completions/Base/Core directory following the following lines
from compaudit:
if [[ -d $_compdir/Base/Core ]]; then
# Add all the Completion subdirectories (CVS-layout)
_i_addfiles=(${_compdir}/*/*(/^M))
b) mkdir plugin's directory in Base
c) simlink completion files (starting with "_") into that subdirectory
c) set _compdir and run compinit
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-26 19:51 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 [this message]
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
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='CAKc7PVCqw_Z+RnjzwEtoRVLSE1A9JSyVQYpg1E=6u5em5qDdkg@mail.gmail.com' \
--to=sgniazdowski@gmail.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).