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
I'm really enjoying using shuttle, so much in fact that I've been trying to add some interactivity to some of my scripts.
Though I have found that it is currently not possible to have interactive sessions through shuttle.
For example if I call a script that uses gum choose foo bar the command simply hangs forever.
Another example: Running an interactive docker container docker run --rm -it alpine returns the error the input device is not a TTY.
I think this could be a valuable addition to shuttle that would open up for using the tool in new and interesting ways.
Thank you for all of your work and for open sourcing shuttle :-)
The text was updated successfully, but these errors were encountered:
This is a great suggestion, I will see what is required to pass the pipes properly internally. It shouldn't be too bad. Right now I believe we just pass raw buffers and stream those out. We if use os.Stdout and os.Stdin instead it should just work (tm)
Hello!
I'm really enjoying using shuttle, so much in fact that I've been trying to add some interactivity to some of my scripts.
Though I have found that it is currently not possible to have interactive sessions through shuttle.
For example if I call a script that uses
gum choose foo bar
the command simply hangs forever.Another example: Running an interactive docker container
docker run --rm -it alpine
returns the errorthe input device is not a TTY
.I think this could be a valuable addition to shuttle that would open up for using the tool in new and interesting ways.
Thank you for all of your work and for open sourcing shuttle :-)
The text was updated successfully, but these errors were encountered: