zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: Danek Duvall <duvall@comfychair.org>,
	Bart Schaefer <schaefer@brasslantern.com>,
	Zsh workers <zsh-workers@zsh.org>
Subject: Re: Completion collision, best way to fix
Date: Fri, 28 Sep 2012 21:53:11 -0400	[thread overview]
Message-ID: <20120929015311.GA66234@redoubt.spodhuis.org> (raw)
In-Reply-To: <20120929011242.GF17010@lorien.comfychair.org>

On 2012-09-28 at 18:12 -0700, Danek Duvall wrote:
> On Fri, Sep 28, 2012 at 07:59:36AM -0700, Bart Schaefer wrote:
> > In practice I'm not sure any of the distribution package maintainers 
> > actually take the step of removing the "irrelevant" functions from the
> > tree; maybe some change the default fpath in /etc/zshrc or the like.
> 
> Given that I'm the zsh integrator for Solaris ...
> 
> Is there a way for the build process to put the "native" OS-specific
> directory ahead of the rest?  If not, would a patch to do that be
> appreciated?  I could take the easy way out and simply drop the BSD _pkg
> from the Solaris zsh package, but it'd be nice not to have to.

You can use --enable-additional-fpath to add entries to the default
fpath; the order used is "site", "additional", "install locations".
Since the list is scanned in order, uniqueness isn't required and you
can just replicate an entry that will appear later.

See the "INSTALL" file for details on the syntax of the option.

If runtime works, then just:
  typeset -U fpath
  fpath=(${fpath[(R)*/Solaris]} $fpath)

-Phil


      parent reply	other threads:[~2012-09-29  2:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  9:33 Baptiste Daroussin
2012-09-28 14:59 ` Bart Schaefer
2012-09-29  1:12   ` Danek Duvall
2012-09-29  1:39     ` Baptiste Daroussin
2012-09-29  1:56       ` Danek Duvall
2012-09-29  3:40       ` Bart Schaefer
2012-09-30 20:47         ` Oliver Kiddle
2012-09-29  1:53     ` Phil Pennock [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=20120929015311.GA66234@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.org \
    --cc=duvall@comfychair.org \
    --cc=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).