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
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Now that #315 has been solved, it is hardly perfect. Here are some suggestions on how to improve it:
Custom actions should have their own autocompletion lists (e. g. pkg info --installed should only autocomplete names of installed DAPs, etc.). This is simple to achieve - when the appropriate element (assistant or action object) has been found, DA would look into a dictionary with object types and custom completion methods, and upon a succesful find would execute the custom completion method.
Completion should honor the number of positional arguments, and nargs a flagged argument has.
Performance improvements
There should be a comfortable way to temporarily switch bash completion on for ./da.py. Technically, it is simple - only replace da with ./da.py in distribution/da.bash and executing the file in bash. This could be done as a setup.py action, maybe?
More ideas for improvements welcome.
The text was updated successfully, but these errors were encountered:
Now that #315 has been solved, it is hardly perfect. Here are some suggestions on how to improve it:
pkg info --installed
should only autocomplete names of installed DAPs, etc.). This is simple to achieve - when the appropriate element (assistant or action object) has been found, DA would look into a dictionary with object types and custom completion methods, and upon a succesful find would execute the custom completion method../da.py
. Technically, it is simple - only replaceda
with./da.py
indistribution/da.bash
and executing the file in bash. This could be done as asetup.py
action, maybe?More ideas for improvements welcome.
The text was updated successfully, but these errors were encountered: