zsh-workers
 help / color / mirror / code / Atom feed
From: Baptiste Daroussin <baptiste.daroussin@gmail.com>
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: Sat, 29 Sep 2012 03:39:24 +0200	[thread overview]
Message-ID: <CAPKC6oL22t6+MxtQcpTOVd8aB-dxgvm8vzpCq+TUAGPFgZt4MA@mail.gmail.com> (raw)
In-Reply-To: <20120929011242.GF17010@lorien.comfychair.org>

2012/9/29 Danek Duvall <duvall@comfychair.org>:
> 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.
>
> Thanks,
> Danek

What we could do is to provide a Unix/_pkg
Which will do the #compdef pkg and call _pkg5 on Solaris and _pkgng on FreeBSD?

if you agree on that I'll do the work and send it to you for review

While you are here will you accept FreeBSD specific completion for
_zfs ? :D like the jail/unjail subcommand

regards,
Bapt


  reply	other threads:[~2012-09-29  1:39 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 [this message]
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=CAPKC6oL22t6+MxtQcpTOVd8aB-dxgvm8vzpCq+TUAGPFgZt4MA@mail.gmail.com \
    --to=baptiste.daroussin@gmail.com \
    --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).