1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
|
[](https://github.com/byron/dua-cli/actions)
[](https://crates.io/crates/dua-cli)
[](https://repology.org/project/dua-cli/badges)
**dua** (-> _Disk Usage Analyzer_) is a tool to conveniently learn about the usage of disk space of a given directory. It's parallel by default and will max out your SSD, providing relevant information as fast as possible. Optionally delete superfluous data, and do so more quickly than `rm`.
[](https://asciinema.org/a/kDnXUOeqBxZVMoWuFNqzfpeey)
### Installation
### Binary Release
#### MacOS
```sh
curl -LSfs https://raw.githubusercontent.com/Byron/dua-cli/master/ci/install.sh | \
sh -s -- --git Byron/dua-cli --crate dua --tag v2.17.4
```
#### MacOS via [MacPorts](https://www.macports.org):
```sh
sudo port selfupdate
sudo port install dua-cli
```
#### MacOS via [Homebrew](https://brew.sh)
```sh
brew update
brew install dua-cli
```
#### Linux
Linux requires the target to be specified explicitly to obtain the MUSL build.
```sh
curl -LSfs https://raw.githubusercontent.com/Byron/dua-cli/master/ci/install.sh | \
sh -s -- --git Byron/dua-cli --target x86_64-unknown-linux-musl --crate dua --tag v2.17.4
```
#### Windows via [Scoop](https://scoop.sh/)
```sh
scoop install dua
```
#### Pre-built Binaries
See the [releases section][releases] for manual installation of a binary, pre-built for many platforms.
[releases]: https://github.com/Byron/dua-cli/releases
#### Cargo
Via `cargo`, which can be obtained using [rustup][rustup]
For _Unix_…
```
cargo install dua-cli
# And if you don't need a terminal user interface (most compatible)
cargo install dua-cli --no-default-features
# Compiles on most platforms, with terminal user interface
cargo install dua-cli --no-default-features --features tui-crossplatform
```
For _Windows_, nightly features are currently required.
```
cargo +nightly install dua-cli
```
#### VoidLinux
Via `xbps` on your VoidLinux system.
```
xbps-install dua-cli
```
#### Fedora
Via `dnf` on your Fedora system.
```
sudo dnf install dua-cli
```
#### Arch Linux
Via `pacman` on your ArchLinux system.
```
sudo pacman -S dua-cli
```
#### NixOS
https://search.nixos.org/packages?channel=23.11&show=dua&from=0&size=50&sort=relevance&type=packages&query=dua
Nix-shell (temporary)
```
nix-shell -p dua
```
NixOS configuration
```
environment.systemPackages = [
pkgs.dua
];
```
#### NetBSD
Via `pkgin` on your NetBSD system.
```
pkgin install dua-cli
```
Or, building from source
```
cd /usr/pkgsrc/sysutils/dua-cli
make install
```
#### Windows
You will find pre-built binaries for Windows in the [releases section][releases].
Alternatively, install via cargo as in
```
cargo +nightly install dua-cli
```
### Usage
```bash
# count the space used in the current working directory
dua
# count the space used in all directories that are not hidden
dua *
# learn about additional functionality
dua aggregate --help
```
### Interactive Mode
Launch into interactive mode with the `i` or `interactive` subcommand. Get help on keyboard
shortcuts with `?`.
Use this mode to explore, and/or to delete files and directories to release disk space.
Please note that great care has been taken to prevent accidential deletions due to a multi-stage
process, which makes this mode viable for exploration.
```bash
dua i
dua interactive
```
### Development
Please note that all the following assumes a unix system. On Windows, the linux subsystem should do the job.
#### Run tests
```bash
make tests
```
#### Learn about other targets
```
make
```
#### But why is…
#### …there only one available backend? `termion` was available previously.
Maintaining both backends seemed more cumbersome than it's worth and add complexity I didn't like anymore. `termion` had its benefits,
but I never liked that it seems to have dropped out of support.
Thus `crossterm` is the only remaining backend and it's very actively developed.
### Acknowledgements
Thanks to [jwalk][jwalk], all there was left to do is to write a command-line interface. As `jwalk` matures, **dua** should benefit instantly.
### Limitations
* Does not show symbolic links at all if no path is provided when invoking `dua`
* in an effort to skip symbolic links, for now there are pruned and are not used as a root. Symbolic links will be shown if they
are not a traversal root, but will not be followed.
* Interactive mode only looks good in dark terminals (see [this issue](https://github.com/Byron/dua-cli/issues/13))
* _easy fix_: file names in main window are not truncated if too large. They are cut off on the right.
* There are plenty of examples in `tests/fixtures` which don't render correctly in interactive mode.
This can be due to graphemes not interpreted correctly. With Chinese characters for instance,
column sizes are not correctly computed, leading to certain columns not being shown.
In other cases, the terminal gets things wrong - I use alacritty, and with certain characaters it
performs worse than, say iTerm3.
See https://github.com/minimaxir/big-list-of-naughty-strings/blob/master/blns.txt for the source.
* In interactive mode, you will need about 60MB of memory for 1 million entries in the graph.
* In interactive mode, the maximum amount of files is limited to 2^32 - 1 (`u32::max_value() - 1`) entries.
* One node is used as to 'virtual' root
* The actual amount of nodes stored might be lower, as there might be more edges than nodes, which are also limited by a `u32` (I guess)
* The limitation is imposed by the underlying [`petgraph`][petgraph] crate, which declares it as `unsafe` to use u64 for instance.
* It's possibly *UB* when that limit is reached, however, it was never observed either.
### Similar Programs
* **CLI:**
* `du`
* [`dust`](https://github.com/bootandy/dust)
* [`dutree`](https://github.com/nachoparker/dutree)
* [`pdu`](https://github.com/KSXGitHub/parallel-disk-usage)
* **TUI:**
* [`ncdu`](https://dev.yorhel.nl/ncdu)
* [`gdu`](https://github.com/dundee/gdu)
* [`godu`](https://github.com/viktomas/godu)
* **GUI:**
* [GNOME's Disk Usage Analyzer, a.k.a. `baobab`](https://wiki.gnome.org/action/show/Apps/DiskUsageAnalyzer)
* Filelight
[petgraph]: https://crates.io/crates/petgraph
[rustup]: https://rustup.rs/
[jwalk]: https://crates.io/crates/jwalk
[tui]: https://github.com/fdehau/tui-rs
|
