From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: zsh-users@zsh.org
Subject: fndir introspection, site-packages documentation
Date: Fri, 13 Mar 2015 23:41:21 +0100 [thread overview]
Message-ID: <20150313224121.GO4524@isis.sigpipe.cz> (raw)
hello,
is there a way to get at the value "fndir" ended up having in configure?
this would be useful in function packaging. i know
/usr/local/share/zsh/site-functions is always used (had to dig, it's not
documented!) but that is not going to please Linux distros, which
generally use --prefix=/usr. i would like to be able to do something
like
sitefndir=$(zsh -c 'print "$ZSHSITEFNDIR"')
a simple Makefile should be able to do the right thing on any operating
system or exotic configuration without user intervention (in this case).
apropos!
there's a *single* occurrence of "site-functions" in zshall(1), a passing
reference coming from the zsh/newuser description in zshmodules(1) of all
places:
If none of the start-up files were found, the module then looks
for the file newuser first in a sitewide directory, usually the
parent directory of the site-functions directory, and if that
is not found the module searches [...]
the configure-time fndir should be mentioned in the $fpath/$FPATH
description in zshparam(1), and this bullet from NEWS absolutely needs
to be there as well:
- The default $fpath/$FPATH is now designed always to include
/usr/local/share/zsh/site-functions. This directory does not need to
exist. Sites that set an explicit site directory can put that in
/etc/zshenv as before. The intention of the new path element is to
increase the likelihood that locally added functions can be found with
the shell running "out of the box", no matter how the shell was
configured.
--
roman
next reply other threads:[~2015-03-13 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 22:41 Roman Neuhauser [this message]
2015-03-14 3:39 ` Bart Schaefer
2015-03-15 2:14 ` Roman Neuhauser
2015-03-15 19:14 ` Bart Schaefer
2015-03-16 9:36 ` patches format " Daniel Shahaf
2015-03-16 10:01 ` Peter Stephenson
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=20150313224121.GO4524@isis.sigpipe.cz \
--to=neuhauser@sigpipe.cz \
--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).