Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repl: disable progress-bar explicitly, fix drawing regression #2249

Closed
wants to merge 1 commit into from

Conversation

dtzWill
Copy link
Member

@dtzWill dtzWill commented Jun 23, 2018

Fixes 'nix repl' having prompt drawn-over after
44de71a.

Apparently repl has ProgressBar enabled like other nix commands,
so after that change after 1 sec an empty line (at least at first)
would be drawn over the prompt, which is of course no good.

AFAICT builds from repl didn't actually use the progress bar anyway
since builds are done in a child via nix-store -r.
Accordingly the easy fix is to disable progress bar for the repl,
but we may want to revisit as progress bar would be nifty
to have for builds done from repl :).


Apologies for the breakage and for not noticing this sooner.

Fixes 'nix repl' having prompt drawn-over after
44de71a.

Apparently repl has ProgressBar enabled like other nix commands,
so after that change after 1 sec an empty line (at least at first)
would be drawn over the prompt, which is of course no good.

AFAICT builds from repl didn't actually use the progress bar anyway
since builds are done in a child via `nix-store -r`.
Accordingly the easy fix is to disable progress bar for the repl,
but we may want to revisit as progress bar would be nifty
to have for builds done from repl :).
@dtzWill
Copy link
Member Author

dtzWill commented Jun 25, 2018

Beep boop, pinging because I feel bad for causing the breakage in an earlier PR.

@dtzWill
Copy link
Member Author

dtzWill commented Jul 10, 2018

Okay it appears nix repl uses progress bar when builtins.fetchurl is invoked, this PR breaks/disables that which is a regression in that regard.

Not sure if there are other cases?

I'll see about other solutions that preserve this behavior...

@dtzWill dtzWill closed this Jul 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant