Marius Bakke writes:
> Robin Templeton writes:
>
>> Seconded! The current behavior seems exactly backwards compared to most
>> *nix tools; if I wanted *less* information from "guix search" I'd
>> manually pipe the output into head or recsel. Perhaps Git-style
>> auto-pagination (i.e. page the
Robin Templeton writes:
> Seconded! The current behavior seems exactly backwards compared to most
> *nix tools; if I wanted *less* information from "guix search" I'd
> manually pipe the output into head or recsel. Perhaps Git-style
> auto-pagination (i.e. page the results when outputting to a
Jan Synacek writes:
> Hello,
>
> I'm going to give honest feedback, since I still care about some things.
>
> I decided to check the new guix-1.1.0 and one of the first things that I ran
> was:
>
> $ guix package -s firefox
>
> The resulting message was infuriating to say the least. The code
On 2020-04-27, 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.
I don't think PAGER is an
Hello,
On Mon, Apr 27, 2020 at 1:59 PM wrote:
> imo the best option would be to page, print or truncate depending on
> an envvar and/or a commandline flag
PAGER="head -20" maybe ?
I'm also of the opinion to respect PAGER. Untruncated ouput if unset.
--
Vincent Legoll
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*
Dear
On Mon, 27 Apr 2020 at 10:39, Jan Synacek 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
Dear,
On Mon, 27 Apr 2020 at 08:12, Jan Synacek wrote:
> On Sun, Apr 26, 2020 at 11:38 AM zimoun wrote:
>> On Sun, 26 Apr 2020 at 10:35, Jan Synacek wrote:
>> > Seriously? Are you seriously forcing your users to either run emacs (or at
>> > least
>> > to set the env variable) or use pipes to
On Mon, Apr 27, 2020 at 4:02 AM Bengt Richter wrote:
> Hi zimoun, Jan,
>
> On +2020-04-26 11:38:01 +0200, zimoun wrote:
> > Dear,
> >
> > On Sun, 26 Apr 2020 at 10:35, Jan Synacek wrote:
> >
> > > Seriously? Are you seriously forcing your users to either run emacs
> (or at least
> > > to set
On Sun, Apr 26, 2020 at 11:38 AM zimoun wrote:
> Dear,
>
> On Sun, 26 Apr 2020 at 10:35, Jan Synacek 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
Hi zimoun, Jan,
On +2020-04-26 11:38:01 +0200, zimoun wrote:
> Dear,
>
> On Sun, 26 Apr 2020 at 10:35, Jan Synacek 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?
>
>
Dear,
On Sun, 26 Apr 2020 at 10:35, Jan Synacek 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
Hello,
I'm going to give honest feedback, since I still care about some things.
I decided to check the new guix-1.1.0 and one of the first things that I ran
was:
$ guix package -s firefox
The resulting message was infuriating to say the least. The code says:
(if (and (not (getenv
13 matches
Mail list logo
