unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Guix does not find packages
Date: Wed, 19 Feb 2020 16:41:00 +0100	[thread overview]
Message-ID: <CAJ3okZ2b4UHW3ysiS03J3XvGmNCQfxEtXsNq__ZUdiyacvDHVg@mail.gmail.com> (raw)
In-Reply-To: <875zg2fwn7.fsf@nckx>

On Wed, 19 Feb 2020 at 16:02, Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> No.  It was a deliberate decision to make ‘guix search’/‘guix
> package -s’ show only the ‘top’ result when stdout is a TTY.  I
> don't like it either.  The argument was that packages are sorted
> with the most relevant one at the top, which would scroll out of
> view.

Even the 'relevance' scoring function should be discussed. ;-)


> I *still* think we should either do nothing, or call $PAGER
> automatically when stdout is a TTY.

I think there is a patch which changes the behaviour to "do nothing"
when INSIDE_EMACS is set.
But from my point of view, the philosophy is to combine "guix search"
with "recsel" to filter the results and then to use "guix show" to
read the information of the package.

(Note that "guix show" shows only one package and it should be able to
accept a list. TODO list ;-))


All the best,
simon

  parent reply	other threads:[~2020-02-19 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 14:38 Guix does not find packages Zelphir Kaltstahl
2020-02-19 14:58 ` John Soo
2020-02-19 15:45   ` Zelphir Kaltstahl
2020-02-19 15:00 ` Joshua Branson
2020-02-19 15:02 ` Tobias Geerinckx-Rice
2020-02-19 15:06   ` John Soo
2020-02-19 15:38   ` Ricardo Wurmus
2020-04-23 20:07     ` Ludovic Courtès
2020-02-19 15:41   ` zimoun [this message]
2020-02-20 15:00     ` Pierre Neidhardt
2020-02-20 14:49   ` Joshua Branson

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=CAJ3okZ2b4UHW3ysiS03J3XvGmNCQfxEtXsNq__ZUdiyacvDHVg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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. 
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).