unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Jan Synacek <jsynacek@redhat.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: hint: Run `guix search ... | less' to view all the results
Date: Mon, 27 Apr 2020 11:44:27 +0200	[thread overview]
Message-ID: <CAJ3okZ3hF66CMBLUP0fGGkA682mawnXzQsBc-jasoKeAL7X=Dg@mail.gmail.com> (raw)
In-Reply-To: <CAPsXM8V3YOQkjtoWNzmmCdr8W3kQ6wr8n9oKij0rioqXHxE_Sg@mail.gmail.com>

Dear

On Mon, 27 Apr 2020 at 10:39, Jan Synacek <jsynacek@redhat.com> wrote:

> Yes, it is truncated in the sense of it doesn't show all the output, unless you use a pipe, redirect or set the env variable. If I run 'guix package -A', it outputs all the available packages without truncating anything and without giving me "helpful" hints. And that's currently 13201 lines on my system. That's how I expect commands to behave and that has been pretty much the normal thing to do since forever.

There is a difference: "guix search" computes a relevance score
depending on the query and the result is sorted by relevance.
Therefore, the few first items should be the most relevant with the
query and page the result should not be "useful" (yes it is debatable!
:-))

There is room of improvement!
For example, 'aptitutde search <query>' returns (by default): name TAB
synopsis. I find that really handy. Even if it would not be the
default, it should be possible to display differently the result of
"guix search".
Another example, it should be possible to sort the result by another
key than the relevance, e.g., to group them by file origin or license
or your-name-it.

Patches welcome. :-)



> While we're at it, let me also give my opinion about supporting PAGER. If it means that if PAGER is set, use it, otherwise don't page, then that's perfectly valid and, in my opinion, how PAGER support is supposed to work. If it means that *unless* something is set *not to use* a pager as some tools currently do (I can only think of some of the systemd tools off top of my head), use pager by default, then that's also backwards. But it's still much better than truncating output by default.

Does Git work the way you suggest all the tools are working?


All the best,
simon

  reply	other threads:[~2020-04-27  9:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  7:59 hint: Run `guix search ... | less' to view all the results Jan Synacek
2020-04-26  9:38 ` zimoun
2020-04-27  1:26   ` Bengt Richter
2020-04-27  8:38     ` Jan Synacek
2020-04-27  9:44       ` zimoun [this message]
2020-04-27 11:58       ` pinoaffe
2020-04-27 17:21         ` Vincent Legoll
2020-04-27 18:36       ` Vagrant Cascadian
2020-04-27  6:12   ` Jan Synacek
2020-04-27  9:29     ` zimoun
2020-06-23 16:05 ` Robin Templeton
2020-06-23 21:06   ` Marius Bakke
2020-06-24  5:30     ` Robin Templeton

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='CAJ3okZ3hF66CMBLUP0fGGkA682mawnXzQsBc-jasoKeAL7X=Dg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=jsynacek@redhat.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).