-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Experimental autocompletion setup scripts #378
Conversation
3559b73
to
45c1107
Compare
Oh sweet! This seems like the easiest way to install autocomplete, I like it! Also down the line we can consider adding a FYI blurb at the beginning of training with the command if the install is not detected. Figuring out how to make this robust may need a bit of thinking.
Lol |
45c1107
to
476b2db
Compare
return True | ||
|
||
|
||
def _exclamation() -> str: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤣
a56d8ed
to
f272ec2
Compare
* Working completion scripts * generate.py => install.py * Uninstall for completions, docs/README updates * Tune emojis, improve concurrency for completion install * wip * Cleanup * Permissions, shebang checks
Prototype for some thoughts @tancik
The tldr is that running:
Will (1) generate a completion script for every dcargs CLI in the
nerfactory/scripts
directory, and then (2) add a one-line update to the user's.bashrc
and/or.zshrc
(after asking for permission).The next shell they open should have completion enabled; I think this should just magically work, but haven't tested very thoroughly.
Misc notes: