From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Package file indexing Date: Thu, 09 Jan 2020 15:21:15 +0100 Message-ID: <8736co90dg.fsf@ambrevar.xyz> References: <20190314204941.GA21065@jasmine.lan> <87mulx9kuv.fsf@nckx> <87zhpx846u.fsf@ambrevar.xyz> <87bm21y2s2.fsf_-_@gnu.org> <87imw7cpe7.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> <87pnqdhkpf.fsf@gnu.org> <87imlt3hr2.fsf@ambrevar.xyz> <87v9pk94ch.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42649) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ipYgl-0004Cc-Il for guix-devel@gnu.org; Thu, 09 Jan 2020 09:21:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ipYgj-0007FZ-TR for guix-devel@gnu.org; Thu, 09 Jan 2020 09:21:31 -0500 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: zimoun Cc: Guix-devel --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable zimoun writes: > Hi again, :-) > > On Thu, 9 Jan 2020 at 13:55, Pierre Neidhardt wrote: > >> What I originally suggested is that we could equivalently do: >> >> guix search "/foo.*bar" python- > > [...] > >> > Time to time, I am looking for header C file or latex style but I do >> > not know the path. I would like to have something like: >> > >> > guix search gmsh.h >> > or >> > guix search ieee*.sty >> >> That's OK, if you know the basename then "/gmsh.h" will match. >> If you only know a substring of the basename, then "/.*gmsh.h" will >> match too. > > My point is just I do not like the key '/' to turn on the file-search > and I prefer "file:". As said elsewhere. :-) Why don't you like it? I don't like "file:" because: =2D It can make for ambiguous command line to the human read (e.g. "file:file:"). =2D It's a new arbitrary syntax which the user must learn to use it, which means they probably won't. The benefit of "/" is that it works _incidentally_. If you are looking for "bin/hg", then `guix search bin/hg` will do the right thing. > What is the purpose of this "list-files" for you? Listing the files of a package like in the example you gave. What I meant is that we already have a subcommand that outputs a property of the given packages, i.e. "guix size". If I'm not mistaken, there is no "guix package" flag that displays any property for the given packages. I am just thinking about keeping consistency across the various subcommands of Guix. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl4XNtsACgkQm9z0l6S7 zH/MMQf/TVeRlbrTB8Q1TF4bFox3VSbeV0CNxTF8ji1IU3m1tmFbeD4aEXnUe5qy z30R44QNOS8eNEdpejVM8mtBl5XSeAjwYuVH5bLj7qNusHfxaxXWYPSd2KrwBnug SZrqL3oJWtNxyerXqF9xKbwW6r6wAInEhV08ZsIjgcEvEFC6K5ZPe+f7PZ2XWl3R ZubAz8ic55amT0Wf/VucVQVsIwB+5/ecpV2WWeQY5YenzJCt963NhANw/EBp9TPa +g5THgUzIgX4nhLrFjEJ51CdrLn0vc+wVJuuFys7Ny7D8M9uznvIw3PomtQUjRE7 8Pivd/627Z8snjbMtUmYwRq7nn+jZg== =b2u/ -----END PGP SIGNATURE----- --=-=-=--