Conversation
|
Cool!
Just to confirm: this PR changes the user interface, right? If I understand it correctly, you've tweaked the |
|
Yes, now it is cleaner. So, instead of showing a progress bar for each file, now only shows the overall progress bar and the current file progress bar. |
|
Cool, sounds good. Let me know when tests are passing and I'll take a closer look! |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #8325 +/- ##
==========================================
- Coverage 68.56% 68.51% -0.06%
==========================================
Files 620 620
Lines 99304 99471 +167
==========================================
+ Hits 68086 68149 +63
- Misses 31218 31322 +104
|
|
Hi,
|
Sorry @Jan9103 I couldn't understand exactly the problem you are having. if you don't want to use the progress bar you don't have to enable it. Also, I don't know if you are testing the |
the problem is: it is enabled by default and cant be disabled - i would like to have it, but also have the option to disable it
i have build the latest commit in your branch (0ab0497) for this test: { lib, fetchFromGitHub, rustPlatform, openssl, zstd, pkg-config, python3, xorg, testers, nushell, nix-update-script}:
rustPlatform.buildRustPackage {
pname = "nushell";
version = "a";
src = fetchFromGitHub {
owner = "Xoffio";
repo = "nushell";
rev = "0ab04970df0c1254fb704b6eb9e2d4d3cecccc75";
sha256 = "sha256-oL2FxB6x7URqD28bFmQ5fNlzguNfCGemALpJq9Q62rI=";
};
cargoSha256 = "sha256-0GAlaio21TsSWKjRWZUe8Uy8k7t4BZm0aciTi+bepUk=";
nativeBuildInputs = [ pkg-config python3 ];
buildInputs = [ openssl zstd xorg.libX11 ];
buildFeatures = [ "default" ];
doCheck = false;
meta = with lib; {
description = "A modern shell written in Rust";
homepage = "https://www.nushell.sh/";
license = licenses.mit;
#maintainers = with maintainers; [ Br1ght0ne johntitor marsam ];
mainProgram = "nu";
platforms = platforms.linux;
};
passthru = {shellPath = "/bin/nu"; };
}for me this is the output: and a realley weird one: (the command is overwritten) the output i would expect is: if i misunderstood the MR or have some issue with my build-setup i apologize for the inconvenience. |
I can reproduce this; looks like the progress bar is enabled without the |
|
@Jan9103 @rgwood Thank you guys. I will be working on this |
|
Hey @rgwood sorry that its taking a bit longer i have a test next Tuesday. After that I will get the fix pushed! Happy coding! |
|
No rush! |
|
@rgwood, @Jan9103 I fixed the issue. |
|
Just tested this. The progress bar no longer appears without However, Screen.Recording.2023-04-06.at.10.30.14.AM.mov |
|
@rgwood that is not intended. I guess I was testing with a simpler folder. Looking into it! Thanks! :) |
terminal getting cleared was fixed. Now the user can cancel the copy process in places they couldn't before.
|
WIP - cleaning code |
|
Hey @rgwood! I believe this is ready for approval. I would like to bring two points to your attention:
Thank you!! let me know if you need my help in any way! |
|
Cool! Sorry but I won't be able to review this in the near future. I've mentioned it on Discord in the hopes that someone else can take a look. |
|
we're working on a replacement for cp that will have a progress bar in #10097. thanks for trying this! |


Description
Cleaner version for the
cpprogress bar. discussed here and hereUser-Facing Changes
The progress bar is not longer one for each file. Instead there are two: one showing the overall progress and the progress of the current file being copy
Tests + Formatting
Check -
cargo fmt --all -- --checkto check standard code formatting (cargo fmt --allapplies these changes)Check -
cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collectto check that you're using the standard code styleCheck -
cargo test --workspaceto check that all tests pass