From owner-freebsd-ports@FreeBSD.ORG Sat Apr 4 18:18:48 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC8B4E6; Sat, 4 Apr 2015 18:18:47 +0000 (UTC) Received: from mail-vn0-x234.google.com (mail-vn0-x234.google.com [IPv6:2607:f8b0:400c:c0f::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97F07830; Sat, 4 Apr 2015 18:18:47 +0000 (UTC) Received: by vnbg62 with SMTP id g62so427198vnb.7; Sat, 04 Apr 2015 11:18:46 -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=K1IDAiSFc/zgq83MpGjyZuMsLOURIOGKyaTaAA0bKD8=; b=zL+qFab02lzCAIWmURIZNwFb4KgV2dl/Jg147V8WRk/9Q3dKNwW+m8ybjCqTeZ6W+F u5ldVso5apdTu02rON5DCz1F3/tpNrJFCMZGCM2OThY1EMEtLI+W/kz/x5B+M2mpMBZF ZX1i425uQoOBlNUk1CYtk7SVlASDn89+ET0ahe5fQte4S8cA3fa4Y6Uk67eFe0EEQMgT WR5bE21kKKGhz+I+YXs4xizhlRpjE4CWKTyhcOH1+AhViEhb75vD/j/H3PrmF4+McQpM HUXEjz5mcxf0SzUrlbtM01sLok89I6/Jtl9wzwNm9+J3ME+hn4u2O95ZG0WdXJkcMQvO Q05Q== X-Received: by 10.52.113.10 with SMTP id iu10mr4537279vdb.88.1428171526584; Sat, 04 Apr 2015 11:18:46 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id fa2sm1851085vdd.17.2015.04.04.11.18.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Apr 2015 11:18:45 -0700 (PDT) Sender: Baptiste Daroussin Date: Sat, 4 Apr 2015 20:18:40 +0200 From: Baptiste Daroussin To: Craig Rodrigues Subject: Re: Share your pkg aliases Message-ID: <20150404181840.GD20155@ivaldir.etoilebsd.net> References: <20150402201909.GD30115@ivaldir.etoilebsd.net> <79DCE8388D31F662B15D7B4A@atuin.in.mat.cc> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d9ADC0YsG2v16Js0" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Mathieu Arnold , pkg , "ports@freebsd.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Apr 2015 18:18:48 -0000 --d9ADC0YsG2v16Js0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 04, 2015 at 11:05:10AM -0700, Craig Rodrigues wrote: > On Sat, Apr 4, 2015 at 1:50 AM, Mathieu Arnold wrote: >=20 > > +--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-completion. > > > > > 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 have > to do any other setup, and things *just work* out of the box. >=20 > It would also give the pkg developers incentive to keep the bash completi= on > 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 accepting patches... you might understand that the number of people involve= d in pkg(8) is pretty low, and lot of work is still needed on the pkg front. I won't personnally spend my time on bash completion because I have imho wa= y too many things to do. >=20 > I just tried zsh, and it looks like the pkg completions work by default > with zsh. Very nice! That is a problem with bash, completion is not officially part of the proje= ct Best regards, Bapt --d9ADC0YsG2v16Js0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUgKwAACgkQ8kTtMUmk6ExxlwCgmd7FZxqCTu2PGKCUbnki6JkH jswAn2rnrf3IB0+X834ooK5huKiljkiV =9u4v -----END PGP SIGNATURE----- --d9ADC0YsG2v16Js0--