zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: Completion collision, best way to fix
Date: Fri, 28 Sep 2012 07:59:36 -0700	[thread overview]
Message-ID: <120928075936.ZM28235@torch.brasslantern.com> (raw)
In-Reply-To: <CAPKC6oKvEWsP2U2iDzRWL9CnacEg2zxVJucenJD-4t8V+MNjpA@mail.gmail.com>

On Sep 28, 11:33am, Baptiste Daroussin wrote:
}
} I want to add the completion function to the main zsh git but I face
} the problems:
} The right place for it would be Completion/BSD/Command, but if I put
} it there it will hide the Completion/Solaris/Command/_pkg5 has they
} both define #compdef pkg
} 
} Is there a nice way to deal with this situation?

Theoretically, you ignore it and put the completion in BSD/Command/.
It's not the only such conflict.

The reason there are separate directories BSD/ and Solaris/ and so on
is to permit the person doing the install on one of those systems to
include or omit only the appropriate subset of completions -- or to
permit the user to omit the irrelevant ones from $fpath, if the
installer configured with --enable-function-subdirs (the default).

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.


  reply	other threads:[~2012-09-28 15:00 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 [this message]
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

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=120928075936.ZM28235@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).