2022-12-17 08:26:00 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.19.0 2.19.0 (2022-12-13) New Features - Remove the handbrake on MacOS which can now deliver the expected performance. Previously it would limit itself to only using 4 threads as it would use a lot of time in user space. This has changed now, and the traversal itself is much more efficient (even though it could definitely be more efficient when comparing to pdu). In any case, counting performance should now greatly improve on M1 MacOS machines. Bug Fixes - resolve stalling issue of previous version. This way, this release is the working version of v2.8.1 . |
2022-09-12 13:50:23 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.18.0 Fixes - Remove a duplicate draw call which would have doubled the time it takes to refresh on user input. This might have been noticable when large amounts of files are displayed. New Features - Automatically resize if the terminal changes in size. |
2022-07-05 18:27:41 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.17.8 2.17.8 (2022-07-05) Bug Fixes remove chrono from the dependency tree. This assures there is no possibility for undefined behaviour to to localtime support used by some of the trash-crate code otherwise. |
2022-06-14 22:16:44 by pin | Files touched by this commit (2) | |
Log message: sysutils/dua-cli: update to 2.17.7 2.17.7 (2022-06-14) Fixes -Improve readability of the currently visible path in light terminal color themes (#129). |
2022-06-12 16:57:43 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.17.6 2.17.6 (2022-06-12) -A maintenance release which should make the ctrl + o feature open files without blocking on linux thanks to an upgrade in the open crate which powers this feauture. |
2022-05-13 23:41:20 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.17.5 2.17.5 (2022-05-13) Bug Fixes -update to latest version of trash to improve trashing on linux See their respective release. |
2022-05-12 11:33:11 by pin | Files touched by this commit (2) | |
Log message: sysutils/dua-cli: update to 2.17.4 2.17.4 (2022-05-12) Bug Fixes -Show all possible information even if one input path could not be read. Previously it would fail entirely without printing anything useful but a relatively non-descript error message. -Open interactive mode even if one of the input paths can't be read. Note that there can still be improvements in indicating which path failed. Also it will happily show an empty user interface in case all input paths are not readable. |
2022-05-10 10:50:29 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.17.3 Bug Fixes -dependency update; upgrade to trash v2.1.1 . The trash upgrade makes sure that trashed items on mount points on freedesktop are actually restorable. |
2022-05-07 06:19:07 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.17.2 A maintenance release that updates all dependencies. Most notably, trash-rs includes a fix for properly moving files into the trash that required parent directories to be created. pkgsrc changes: Allow default features on Linux. |
2022-03-20 17:24:01 by pin | Files touched by this commit (3) | |
Log message: sysutils/dua-cli: update to 2.17.1 Improvements to aggregate progress reporting Previously, aggregate mode progress reports were handled by an infinitely-looping thread carrying a 64-bit atomic of the current count, which it would print periodically. This resulted in #99 - breaking on platforms without 64-bit atomics, for which a feature was added to disable it. It also implied a race condition, where the "Enumerating ..." message could be printed after results had been gathered but before dua exited. Additionally, part of the status message could be left on the display if the first line of a report was too short to cover it. This commit should resolve these: The 64-bit atomic counter is replaced with an 8-bit AtomicBool All printing is controlled from the main thread The first line is cleared prior to printing a report The only notable drawback I see with this approach is that progress reporting can sometimes be delayed, since the display is only evaluated for update during periods the aggregation loop makes progress. The practical difference appears relatively minor. Since this should resolve #99, the aggregate-scan-progress feature is removed. Special thanks to @Freaky for the contribution! BREAKING change for package maintainers The aggregate-scan-progress feature was removed as it shouldn't be required anymore. |