From mboxrd@z Thu Jan 1 00:00:00 1970 From: pinoaffe@airmail.cc Subject: Re: hint: Run `guix search ... | less' to view all the results Date: Mon, 27 Apr 2020 11:58:52 +0000 Message-ID: References: <20200427012635.GA4379@LionPure> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60146) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jT2Pf-0003rP-PV for guix-devel@gnu.org; Mon, 27 Apr 2020 07:59:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jT2Pf-000132-HR for guix-devel@gnu.org; Mon, 27 Apr 2020 07:59:03 -0400 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: Jan Synacek Cc: Guix Devel , Guix-devel 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