From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: The default $fpath
Date: Sat, 06 Sep 2014 20:44:05 -0700 [thread overview]
Message-ID: <140906204405.ZM18404@torch.brasslantern.com> (raw)
In-Reply-To: <20140907000454.74cda356@pws-pc.ntlworld.com>
On Sep 7, 12:04am, Peter Stephenson wrote:
}
} I think it needs to be additional. What I'm less clear about is where
} it would go in the path.
To satisfy the original request, it'd have to be both additional, and
a fixed location independent of the locations chosen by the package
builder. I'm not sure it's possible to satisfy the latter constraint.
As Frank pointed out, configure already has --enable-additional-fpath
which adds locations to the end of the path. One possibility is to
declare a default value for that.
Or we could do the very zsh-ish thing of inventing TWO such locations
and putting one at each end of the fpath.
} If we made the change, we might, however, want to document that from
} now on /usr/local/share/zsh/site-functions is recommended if the
} functions are to be available to all instances of zsh.
Shouldn't we document that already/anyway? That is after all the first
directory in the existing default fpath.
(Given that, it would seem we already have a location at the beginning
of the path and if we need anything we need one at the other end.)
next prev parent reply other threads:[~2014-09-07 3:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 12:00 Tanu Kaskinen
2014-09-06 16:06 ` Frank Terbeck
2014-09-06 18:45 ` Peter Stephenson
2014-09-06 19:10 ` Frank Terbeck
2014-09-06 23:04 ` Peter Stephenson
2014-09-07 3:44 ` Bart Schaefer [this message]
2014-09-07 18:31 ` Peter Stephenson
2014-09-07 19:37 ` Vin Shelton
2014-09-07 19:53 ` Tanu Kaskinen
2014-09-07 20:40 ` Peter Stephenson
2014-09-07 21:01 ` Bart Schaefer
2014-09-08 10:23 ` Peter Stephenson
2014-09-08 11:16 ` Frank Terbeck
2014-09-20 19:04 ` Peter Stephenson
2014-09-20 19:36 ` Peter Stephenson
2014-09-20 20:00 ` 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=140906204405.ZM18404@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).