-
Notifications
You must be signed in to change notification settings - Fork 28
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
Interactive mode - why not? #42
Comments
A related requirement would be the possibility of specifying some, but not all, options as interactive, e.g. password options and the like. This is common in database command line clients where most options are specified on the command line, but the password is prompted for interactively. Thus, it would make sense to separate between masked Edit: Thank you for putting together this very useful library. It is really appreciated! |
I was thinking of making some options "completable", that is, if missing, they would be asked for interactively. What do you think? |
That sounds like it would satisfy my requirement quite nicely! So long as it only tries asking for them if a tty is present. Otherwise it would cause weird behavior when running the app in daemon mode. I just about mucked about implementing support for interactive options in a fork (ps not quite complete or tested): snorremd@4293ea2 Line 163 in the The (filter (complement #{:foo :bar}) [{:option "foo"} {:option "bar"}])
=> ({:option "foo"} {:option "bar"}) So that might be a bug? Thanks again. |
If we have:
Why shouldn't we have:
The text was updated successfully, but these errors were encountered: