From owner-freebsd-pkg@FreeBSD.ORG Sat Apr 4 19:05:34 2015 Return-Path: Delivered-To: pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C135BD49; Sat, 4 Apr 2015 19:05:34 +0000 (UTC) Received: from mail-vn0-x22b.google.com (mail-vn0-x22b.google.com [IPv6:2607:f8b0:400c:c0f::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BF61D3A; Sat, 4 Apr 2015 19:05:34 +0000 (UTC) Received: by vnbf1 with SMTP id f1so13323vnb.5; Sat, 04 Apr 2015 12:05:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=jhrIf9i3O91Ds5O5CumtsqhGry1O4yq7d4lSm85qYsk=; b=qEIG2OLUJqaQMiv9nbuDo/0DxAZx9x/S5tPRxe6TDaZ+zKMANOaz428Urrs2RB9Qk3 VJOn9n0sCvpq7dZtpowPPbdw6kTsRts90NAwqXatZ6cgx8EIzBbqc4gGQDetOWuYULX9 UOl/dZPmUm/KRyENmvE+E70QTE7MO1x7xGbuRBVsMXpAzqI1/R0JS8YRu2f59Hj7bqzJ Zty77Lan4S7HffG5eKYtSMJzWYgcRMFCR5+qXnQLb3VIDvShC6N/s3QeUMKyRbYs3nxG NiKxjfonJ0f2O8YwNSThj+WwamdH+TZFw1Iga3HO6H/LeaSls+Jl4vcVzXK4+tNdmZLg 3sUg== X-Received: by 10.52.254.2 with SMTP id ae2mr4650148vdd.33.1428174333534; Sat, 04 Apr 2015 12:05:33 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id cw4sm1869036vdd.14.2015.04.04.12.05.30 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Apr 2015 12:05:31 -0700 (PDT) Sender: Baptiste Daroussin Date: Sat, 4 Apr 2015 21:05:27 +0200 From: Baptiste Daroussin To: Craig Rodrigues Subject: Re: Share your pkg aliases Message-ID: <20150404190527.GF20155@ivaldir.etoilebsd.net> References: <20150402201909.GD30115@ivaldir.etoilebsd.net> <79DCE8388D31F662B15D7B4A@atuin.in.mat.cc> <20150404181840.GD20155@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pgaa2uWPnPrfixyx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: pkg , "ports@freebsd.org" X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Apr 2015 19:05:34 -0000 --Pgaa2uWPnPrfixyx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 04, 2015 at 12:00:55PM -0700, Craig Rodrigues wrote: > On Sat, Apr 4, 2015 at 11:18 AM, Baptiste Daroussin > wrote: >=20 > > On Sat, Apr 04, 2015 at 11:05:10AM -0700, Craig Rodrigues wrote: > > > On Sat, Apr 4, 2015 at 1:50 AM, Mathieu Arnold wrot= e: > > > > > > > +--On 3 avril 2015 12:47:31 -0700 Craig Rodrigues| > > > > | It's a minor thing, but tab completions are really nice for > > usability. > > > > | bash shell users can use this, but zsh also has a way to read bash > > > > | completion scripts. > > > > > > > > It's picked up automatically when you install shells/bash-completio= n. > > > > > > > > > > > Cool. shells/bash-completion *does* work with pkg. > > > It would be cool if shells/bash-completion was automatically installed > > > when the bash port is installed, so that the average user does not ha= ve > > > to do any other setup, and things *just work* out of the box. > > > > > > It would also give the pkg developers incentive to keep the bash > > completion > > > updated and in sync as new pkg sub commands and command flags are > > > added. > > > > None of the pkg developpers are using bash or bash completion so ... we= are > > >=20 >=20 > That may be true, but I see that a few pkg committers use zsh. >=20 > One thing that I can see that the pkg project could do is > instead of having separate completion files for bash and zsh, > only have one for bash. zsh can grok bash completions. > That way you will only have one file to maintain, and zsh and bash users > can test it and benefit from it. >=20 > For example, right now, if I "pkg install tmux", if I use zsh as my shell, > it groks the bash completions that come with the tmux port. >=20 > I agree with you that it is unfortunate that bash completions is not > part of bash itself. Maybe we can add a dependency to > shells/bash if bash is installed, it installs the bash-completion port as > well. >=20 > It's a minor thing, but improves the out of the box user experience of the > command-line. As a maintainer of zsh, and heavy user of zsh I will never base any complet= ion for zsh on bash completion, for simple reasons I consider bash completion hackish, and most of the time inefficient on zsh. We are speaking of opensource software, if bash users want to see their completion improved then they should just provide patches. I am a zsh guy a= nd I do not update zsh completion because of ENOTIME already so... Best regards, Bapt --Pgaa2uWPnPrfixyx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUgNfcACgkQ8kTtMUmk6ExFLACfQ51OcujjxF8mtKOl12XGZtgO QHsAoLUo9A3Nt2ZzXMAikv5j0OIbq8kG =/qDP -----END PGP SIGNATURE----- --Pgaa2uWPnPrfixyx--