From: Dan Nelson <dnelson@allantgroup.com>
To: Jason Price <jprice@cyberbuzz.gatech.edu>
Cc: zsh-users@sunsite.dk
Subject: Re: compinit, $fpath, and recursive searching.
Date: Thu, 9 Dec 2004 20:27:51 -0600 [thread overview]
Message-ID: <20041210022750.GA4956@dan.emsphone.com> (raw)
In-Reply-To: <20041209180711.A7960@redfish.gatech.edu>
In the last episode (Dec 09), Jason Price said:
> When I install zsh from source, if I set the $fpath to
>
> fpath=( /usr/local/share/zsh/$ZSH_VERSION/functions )
>
> it works right.
If you had left in zsh's default fpath elements, it would have worked
better:
fpath=( $fpath /more/fpath/paths )
> What are the appropriate setting(s) when you divide up the completion
> functions into directories?
If you have subdirs inside site-functions, or some other local
directory, just use a wildcard to enumerate them ( /primary/path/**/ ) .
The default value of $fpath on my s10b72 box is:
( /usr/sfw/share/zsh/site-functions
/usr/sfw/share/zsh/4.2.1/functions/Completion
/usr/sfw/share/zsh/4.2.1/functions/Completion/AIX
/usr/sfw/share/zsh/4.2.1/functions/Completion/BSD
/usr/sfw/share/zsh/4.2.1/functions/Completion/Base
/usr/sfw/share/zsh/4.2.1/functions/Completion/Cygwin
/usr/sfw/share/zsh/4.2.1/functions/Completion/Debian
/usr/sfw/share/zsh/4.2.1/functions/Completion/Linux
/usr/sfw/share/zsh/4.2.1/functions/Completion/Mandrake
/usr/sfw/share/zsh/4.2.1/functions/Completion/Redhat
/usr/sfw/share/zsh/4.2.1/functions/Completion/Unix
/usr/sfw/share/zsh/4.2.1/functions/Completion/X
/usr/sfw/share/zsh/4.2.1/functions/Completion/Zsh
/usr/sfw/share/zsh/4.2.1/functions/MIME
/usr/sfw/share/zsh/4.2.1/functions/Misc
/usr/sfw/share/zsh/4.2.1/functions/Prompts
/usr/sfw/share/zsh/4.2.1/functions/TCP
/usr/sfw/share/zsh/4.2.1/functions/Zftp
/usr/sfw/share/zsh/4.2.1/functions/Zle )
--
Dan Nelson
dnelson@allantgroup.com
prev parent reply other threads:[~2004-12-10 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 23:07 Jason Price
2004-12-10 2:27 ` Dan Nelson [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=20041210022750.GA4956@dan.emsphone.com \
--to=dnelson@allantgroup.com \
--cc=jprice@cyberbuzz.gatech.edu \
--cc=zsh-users@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).