From: pinoaffe@airmail.cc
To: Jan Synacek <jsynacek@redhat.com>
Cc: Guix Devel <guix-devel@gnu.org>,
Guix-devel <guix-devel-bounces+pinoaffe=airmail.cc@gnu.org>
Subject: Re: hint: Run `guix search ... | less' to view all the results
Date: Mon, 27 Apr 2020 11:58:52 +0000 [thread overview]
Message-ID: <df17ee73e78a9f8ef1cee293c2a585d7@airmail.cc> (raw)
In-Reply-To: <CAPsXM8V3YOQkjtoWNzmmCdr8W3kQ6wr8n9oKij0rioqXHxE_Sg@mail.gmail.com>
On 2020-04-27 08:38, Jan Synacek wrote:
> 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.
imo the best option would be to page, print or truncate depending on
an envvar and/or a commandline flag
next prev parent reply other threads:[~2020-04-27 11:59 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 [this message]
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=df17ee73e78a9f8ef1cee293c2a585d7@airmail.cc \
--to=pinoaffe@airmail.cc \
--cc=guix-devel-bounces+pinoaffe=airmail.cc@gnu.org \
--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).