all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: mikadoZero <mikadozero@yandex.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull package output truncated
Date: Wed, 17 Apr 2019 22:07:37 -0400	[thread overview]
Message-ID: <cucbm142hhy.fsf@yandex.com> (raw)
In-Reply-To: <87h8aw72wp.fsf@gnu.org>


Thank you for pointing out `guix pull -l` for this.

Ludovic Courtès writes:

> Hello!
>
> mikadoZero <mikadozero@yandex.com> skribis:
>
>> Recently the output of guix pull has changed.  It no longer gives the
>> complete output for the "New in this revision" section.
>
> For the record, I did that after seeing that, when you don’t upgrade
> every two days or so, your screen could easily be filled by tens of
> lines of packages.
>
>> Is there a flag I can pass to guix pull to turn off this truncation.  I
>> found it informative to be able to see all the packages that were being
>> added and upgraded and would like to continue to be able to see all the
>> packages.
>
> There’s currently no flag to change this behavior.  Instead, you have to
> run ‘guix pull -l’ but it’s arguably not very convenient.
>
> Perhaps we could add an environment variable specifying whether/how to
> truncate?  I’d keep the default as it is now.
>
> Thoughts?
>
> Ludo’.

      parent reply	other threads:[~2019-04-18  2:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13 12:59 guix pull package output truncated mikadoZero
2019-04-17 21:11 ` Ludovic Courtès
2019-04-17 22:44   ` Tobias Geerinckx-Rice
2019-04-18 15:25     ` Ludovic Courtès
2019-04-18 16:29       ` Pierre Neidhardt
2019-04-19 12:12         ` Ludovic Courtès
2019-04-19 13:02           ` Pierre Neidhardt
2019-04-18 17:27       ` Tobias Geerinckx-Rice
2019-04-18  2:07   ` mikadoZero [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cucbm142hhy.fsf@yandex.com \
    --to=mikadozero@yandex.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.