From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Package file indexing Date: Thu, 09 Jan 2020 13:57:45 +0100 Message-ID: <87sgko948m.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> <462f35f7596f7318d2b34cc300a7e27a69d2072c.camel@riseup.net> 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]:49588) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ipXNl-0001er-9B for guix-devel@gnu.org; Thu, 09 Jan 2020 07:57:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ipXNk-0000T5-4w for guix-devel@gnu.org; Thu, 09 Jan 2020 07:57:49 -0500 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:40733) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ipXNj-0000K5-Rc for guix-devel@gnu.org; Thu, 09 Jan 2020 07:57:48 -0500 In-Reply-To: <462f35f7596f7318d2b34cc300a7e27a69d2072c.camel@riseup.net> 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: raingloom , zimoun Cc: Guix-devel --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable raingloom writes: > What about files in root (so, ones with no slashes in their path, at > least in your syntax) and files you don't know the full path of, only > their basename? For a file at root, e.g. the "bin" folder, you can match with "/bin". If you only know the basename, same: "/hg" will match "/bin/hg". If you only know a substring, then you can use a regexp: "/.*my-substring" > Do you search for every word as a file path, just in case it might be > one? Yes. > To avoid confusion, I think this should be an option/subcommand of > search. Something like -path and -name in find(1). I believe that there is no point in matching slashes ("/") in the synopsis / description, so it's safe enough to use as a filter meant to match only file names. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl4XI0kACgkQm9z0l6S7 zH/vEQf/WCI9ixQRfZ9/9O1CS5/alYqOWEAfWcbdx2qYTSHTRQbQWUwyTRe4dy/3 uTBXIAS0WMHF/GhYeYAl4k9wkQxt7WWyDALCfLdLOs+2lBbzt22FWHpngGrtf37Q xDWA9LJZJpyMP39yIqT4MTYV0NdRlCsI9BuBybwE1v486lNjcFqw9Ycuf75MjCFv rvf80SVQiipi2tPUvNrhrFcYoxB7ndN1lwTx4zlzZyAezs1Es/aGPF7FQuTtWpMj 0v6OLrkTdWTAUAR1Dl5ZmtGGI1rqiEdhhCKAxMfw8YcT2vvlZiYVG9UfNIJp+Za6 as6mQg/2EawnRuXwMclNv9ScA92Mrw== =zGxD -----END PGP SIGNATURE----- --=-=-=--