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
Suggestion: size support (column, sorting) #84
Comments
I don't want to implement a full |
Maybe in the future it'll be possible to run a disk analyzer as a service that will set extra properties to the nodes like |
Also supports sorting by inode size. Closes: #84
Also supports sorting by inode size. Closes: #84
Also supports sorting by inode size. Closes: #84
Also supports sorting by inode size. Closes: #84
Also supports sorting by inode size. Closes: #84
Also supports sorting by inode size. Closes: #84
Follow symlink to files to it's parent directory. Also, hide file size for directories. Ref: #84
Follow symlink to files to it's parent directory. Also, hide file size for directories. Ref: #84
Follow symlink to files to it's parent directory. Also, hide file size for directories. Ref: #84
What are your thoughts on adding support for file sizes? To have a column with file size, to be able to sort by them?
ncdu
integration as you've shown in wiki is nice, and maybe it's enough, I was just thinking about it, and (a) for me personally, a size column would probably be more interesting than mime or index, and (b) some operations like system cleaning although possible to do inncdu
, might be more pleasant to do inxplr
.bonus points: directory sizes, something that even
exa
doesn't support 🙂The text was updated successfully, but these errors were encountered: