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:29:51 +0200	[thread overview]
Message-ID: <CAJ3okZ2ERfDB4UdoTEcNPEf3uQ8YLtcD1_kU59Mro_+-32Layg@mail.gmail.com> (raw)
In-Reply-To: <CAPsXM8UtZj2BJm7ghcW4qq__awzbU7cZeGLSUppi2oojM77Rbg@mail.gmail.com>

Dear,

On Mon, 27 Apr 2020 at 08:12, Jan Synacek <jsynacek@redhat.com> wrote:
> On Sun, Apr 26, 2020 at 11:38 AM zimoun <zimon.toutoune@gmail.com> wrote:
>> On Sun, 26 Apr 2020 at 10:35, Jan Synacek <jsynacek@redhat.com> wrote:

>> > Seriously? Are you seriously forcing your users to either run emacs (or at least
>> > to set the env variable) or use pipes to get the entire search result?
>>
>> It is "known" that Guix should respect the PAGER variable [1,2] and it
>> is already a feature request [3].
>>
> Why do you want to make things complicated? What's wrong with *just showing the entire output*? And let users decide if they want to use a pager, recsel, emacs or redirect the output somewhere else.
>
> I mean you run a command and the command shows its output. It makes me kind of sad that there even has to be a discussion about this.
>
>> [1] https://lists.gnu.org/archive/html/guix-devel/2020-02/msg00039.html
>> [2] https://lists.gnu.org/archive/html/help-guix/2020-02/msg00150.html
>> [3] https://lists.gnu.org/archive/html/help-guix/2020-02/msg00154.html


I do not have a strong opinion.
Personally, I do not find the default behaviour really handy and I
(almost) always pipe with 'recsel -C -P name' because I do not find
handy neither to display all the package fields by default. Well,
taste and colour. :-)
And my answer was just to point you that it is not an arbitrary
choice. And all choices can be discussed. ;-)


All the best,
simon

  reply	other threads:[~2020-04-27  9:30 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
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 [this message]
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=CAJ3okZ2ERfDB4UdoTEcNPEf3uQ8YLtcD1_kU59Mro_+-32Layg@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).