You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But a quick attempt[1] at using bashcompinit didn't work flawlessly. (what is the policy on including bash completions btw?)
A crude way of finding out which tools are missing completion definitions:
# In directory util-linux/bash-completion
for x in *; do
if [[ -z $_comps[$x] ]]; then echo $x; fi
done
This lists almost all the tools. (but it isn't a perfect test. If anyone know of a better way of looking up how a given command is completed I'd be interested)
[1]
bashcompinit
source ./lsblk # is this the correct way?
lsblk --output F<tab>
# _lsblk_module:43: command not found: compopt
The text was updated successfully, but these errors were encountered:
https://en.wikipedia.org/wiki/Util-linux
These have upstream bash completion definitions.
But a quick attempt[1] at using
bashcompinit
didn't work flawlessly. (what is the policy on including bash completions btw?)A crude way of finding out which tools are missing completion definitions:
This lists almost all the tools. (but it isn't a perfect test. If anyone know of a better way of looking up how a given command is completed I'd be interested)
[1]
The text was updated successfully, but these errors were encountered: