12 ms·
The Bash CLI is my file manager. So I've got ncdu built right in. Try it, you'll love it. I almost never touch the rodent.
by dotancohen 4y ago
The Bash CLI is my file manager. So I've got ncdu built right in. Try it, you'll love it. I almost never touch the rodent.
- tetris11 4y agoExcept that running "ls" doesn't show you the directory content size, and "ncdu" requires the user to make a tea first. The above poster is right in saying that having this built-in to the filesystem metrics would be a huge win.
- j33zusjuice 4y agoBut `du -h -d1` does, though, or `tree —-du -h`.
- Wingy 4y agoduc! use a cronjob for `duc index`, then you can use `duc ui` to see the index. it doesn’t immediately update on change so it’s not quite what you’re looking for, but it might be the closest thing.
- danparsonson 4y agoWow thank you for that! This whole thread is great - I've been missing a utility like this for ages but never took the time to go hunting for it.
- dotancohen 4y agoIf I ever need to know a directory size, du -sh foo/ is already muscle memory, and if OP needs it often he can alias it.
- aabbcc1241 4y agoThe time to scan with ncdu on directory with massive number of directories and files can be long and you don't get progressive stats. I made jsdu to get progressive (and recursive) size. I mostly only use jsdu on a few top levels directories, and use ncdu for the rest or after the stats is cached by jsdu. You can install jsdu with "sudo npm i -g jsdu" or run it without install with "npx jsdu"