-
Notifications
You must be signed in to change notification settings - Fork 8
Use a separate "execute" for running bash commands in containers #100
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
Conversation
|
||
execute.desc 'bash command to run (wrap argument in quotes)' | ||
execute.arg_name 'BASH_COMMAND' | ||
execute.flag [:c, :command], type: String, required: true |
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.
Use %i or %I for an array of symbols.
(we already had |
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.
Whatever is fine, it was fine before in my opinion but whatever you think is clear.
I decided that having the
--command
flag on thebash
command made the situation more complicated than it should be, especially when introducing the--all
switch, so i separatedexecute
to its own command namespace. I think it's better this way.Also addresses a bug where
Open3
would block an interactive session (bug is on master but was not released)