From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 41183-done@debbugs.gnu.org
Subject: bug#41183: [PATCH] guix package, show: Support multiple queries.
Date: Mon, 11 May 2020 22:25:45 +0200 [thread overview]
Message-ID: <87ftc6fcc6.fsf@gnu.org> (raw)
In-Reply-To: <20200510234044.14251-1-zimon.toutoune@gmail.com> (zimoun's message of "Mon, 11 May 2020 01:40:44 +0200")
Hello,
zimoun <zimon.toutoune@gmail.com> skribis:
> * guix/scripts/package.scm (process-query): Show multiple queries.
> * guix/scripts/show.scm (guix-show): Reverse to display in order.
Yay, applied!
> Note that:
>
> 1. "guix package" processes from right to left.
> 2. "guix show" processes from left to right.
>
> It is how "guix packages" is implemented. However, it appears more natural to
> display in order; that's why "guix show" reverses the order.
>
> 3. Because dealing with multiple different queries does not seems "keep it
> simple", "guix package" starts with the last query (the most of left) and
> then processes all the queries corresponding to this one.
>
>
> For example,
>
> a) guix package --show=emacs --search=hello --show=libffi
> will show the packages 'emacs' and 'libffi', skipping 'search'.
>
> b) guix package --show=emacs --show=libffi --search=hello
> will search the package 'hello', skipping 'show'.
>
> It is already how '--search' works and has been extended to '--show'. Does it
> need to be documented in the manua?
Weirdness. I think we should improve all that rather than document it,
addressing also some of the issues raised in
<https://issues.guix.gnu.org/issue/40549>.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-05-11 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 23:37 [bug#41183] [PATCH 0/1] guix package, show: Support multiple queries zimoun
2020-05-10 23:40 ` [bug#41183] [PATCH] " zimoun
2020-05-11 20:25 ` Ludovic Courtès [this message]
2020-05-11 21:48 ` zimoun
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=87ftc6fcc6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41183-done@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).