unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: Re: keep spinning even without new line
Date: Sat, 29 Dec 2018 18:57:10 -0800	[thread overview]
Message-ID: <87pntjrabd.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87muootkms.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

On 2018-12-29, Ricardo Wurmus wrote:
> when using “guix package -i” the build log lines are replaced with a
> spinner character.  In some cases, the build log does not produce new
> lines for a long time, so that the spinner appears to be stuck.

> What do you think of advancing the spinner even when the build log is
> not verbose enough to trigger the display of the next character?  How
> can this be accomplished?

Are you proposing that the spinner spins even when there's no indication
that anything is actually happening? Or is there some source of
information other than the build log output?

It could spin multiple times for each line, and space them out over
time... (multiple lines in the same time-window might only spin X number
of times)

To me, it would make sense that the spinner should stop spinning if the
build is stuck or just not very active... otherwise, it's not providing
useful information to the person watching...


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2018-12-30  2:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 15:31 keep spinning even without new line Ricardo Wurmus
2018-12-30  0:21 ` Ricardo Wurmus
2019-01-05 18:15   ` Ludovic Courtès
2018-12-30  2:57 ` Vagrant Cascadian [this message]
2018-12-30  6:25   ` Ricardo Wurmus

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=87pntjrabd.fsf@ponder.i-did-not-set--mail-host-address--so-tickle-me \
    --to=vagrant@debian.org \
    --cc=guix-devel@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 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).