-
Notifications
You must be signed in to change notification settings - Fork 246
Open
Description
Hi,
I thought I'd give dust a try, but was disappointed in the behaviour of the tab completion (in Bash in Debian Trixie), i.e. when I do:
dust <TAB><TAB>
the result isn't what I expect. Here's a comparison with du, where I expect the completion to show me two subdirectories: a and b:
$ ls
a b
$ du
a/ b/
$ dust
-d -r -v -j --config --no-colors --invert-filter --stack-size --version
-T -c -e -M --number-of-lines --force-colors --filter --output-json [PATH]...
-n -C -t -A --full-paths --no-percent-bars --file-types --mtime
-p -b -w -y --ignore-directory --bars-on-right --terminal-width --atime
-X -B -P -m --ignore-all-in-file --min-size --no-progress --ctime
-I -z -D -h --dereference-links --screen-reader --print-errors --files0-from
-L -R -F -V --limit-filesystem --skip-total --only-dir --collapse
-x -f -o --depth --apparent-size --filecount --only-file --filetime
-s -i -S --threads --reverse --ignore-hidden --output-format --help
Interestingly, I do get the behaviour I desire if there's a comment on the line, i.e. like this:
$ dust # some comment
b/ a/
Version: 1.2.0
Metadata
Metadata
Assignees
Labels
No labels