From: zimoun <zimon.toutoune@gmail.com>
To: raingloom <raingloom@riseup.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Package file indexing
Date: Mon, 6 Jan 2020 17:56:03 +0100 [thread overview]
Message-ID: <CAJ3okZ1GXZz+DF0nMm8tG9X=k8Jx0f7WbB6D9qbTVcwzt2-UcQ@mail.gmail.com> (raw)
In-Reply-To: <462f35f7596f7318d2b34cc300a7e27a69d2072c.camel@riseup.net>
Dear,
On Fri, 3 Jan 2020 at 17:01, raingloom <raingloom@riseup.net> wrote:
> On Thu, 2020-01-02 at 23:50 +0100, zimoun wrote:
> > 2. because it allows (in the near future) mixed research: "guix
> > search bin/hg python" applying the "python" filter only to the
> > packages returned by "bin/hg". And "guix search python bin/hg" search
> > the binary file "hg" only to the packages matching "python.
> 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?
I agree.
This second bullet was about composing the "regular package" search
and the "file" search; not really about the syntax to switch between
the two kind of search. :-)
Below the quoting you did, I also described something like "guix
search gmsh.h". ;-)
The syntax '/' should be an option but not the only one, IMHO. We can imagine:
- guix search file:gmsh.h gimp
- guix search bin/gmsh gimp
- guix search file:ieee*.sty bin/gmsh latex
- guix search file:bin/gmsh
- guix search package:gimp
etc.
> To avoid confusion, I think this should be an option/subcommand of
> search. Something like -path and -name in find(1).
I agree that explicit keywords, e.g., "file:" and "package:", avoid confusion.
All the best,
simon
next prev parent reply other threads:[~2020-01-06 16:56 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 18:31 Improve package search mikadoZero
2019-03-14 20:49 ` Leo Famulari
2019-03-14 22:01 ` Tobias Geerinckx-Rice
2019-03-14 22:09 ` Tobias Geerinckx-Rice
2019-03-14 22:46 ` Pierre Neidhardt
2019-03-14 23:09 ` Tobias Geerinckx-Rice
2019-03-23 16:27 ` Package file indexing Ludovic Courtès
2019-03-25 8:46 ` Pierre Neidhardt
2019-03-26 12:41 ` Ludovic Courtès
2020-01-02 17:12 ` Pierre Neidhardt
2020-01-02 19:15 ` Christopher Baines
2020-01-03 11:26 ` Ludovic Courtès
2020-01-09 11:19 ` Pierre Neidhardt
2020-01-09 12:24 ` zimoun
2020-01-09 13:01 ` Pierre Neidhardt
2020-01-09 16:49 ` Christopher Baines
2020-01-10 12:35 ` Pierre Neidhardt
2020-01-10 13:30 ` Christopher Baines
2020-01-11 18:26 ` Pierre Neidhardt
2020-01-12 13:29 ` Christopher Baines
2020-01-13 14:28 ` Pierre Neidhardt
2020-01-13 17:57 ` Christopher Baines
2020-01-13 18:21 ` Pierre Neidhardt
2020-01-13 19:45 ` Christopher Baines
2020-01-14 9:21 ` Pierre Neidhardt
2020-01-02 22:50 ` zimoun
2020-01-03 16:00 ` raingloom
2020-01-06 16:56 ` zimoun [this message]
2020-01-09 13:01 ` Pierre Neidhardt
2020-01-09 13:53 ` zimoun
2020-01-09 14:14 ` Pierre Neidhardt
2020-01-09 14:36 ` zimoun
2020-01-09 15:38 ` Pierre Neidhardt
2020-01-09 16:59 ` zimoun
2020-01-09 12:57 ` Pierre Neidhardt
2020-01-09 12:55 ` Pierre Neidhardt
2020-01-09 14:05 ` zimoun
2020-01-09 14:21 ` Pierre Neidhardt
2020-01-09 14:51 ` zimoun
2020-01-09 15:41 ` Pierre Neidhardt
2020-01-09 17:04 ` zimoun
2020-01-09 17:27 ` Pierre Neidhardt
2020-01-15 16:23 ` Pierre Neidhardt
2020-01-15 17:27 ` Nicolò Balzarotti
2020-01-15 18:02 ` Pierre Neidhardt
2020-01-15 22:14 ` Ludovic Courtès
2019-03-16 2:11 ` Improve package search mikadoZero
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ1GXZz+DF0nMm8tG9X=k8Jx0f7WbB6D9qbTVcwzt2-UcQ@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=raingloom@riseup.net \
/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.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).