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
First of all, I'm running runme on Windows, but using Git bash as the default shell (added to PATH as well)
When I run shell commands in interactive mode, the integrated terminal is opened up and the code is executed successfully
However, I want to print the cell output to the notebook, so I turned off the interactive mode. However, it seems that the commands are now wrong, even though it executed fine previously
When checking the output tab it shows something like this
Also, I'm learning SQL using the BigQuery emulator, hence I need all cell to produce notebook output, but it seems that there is no way to turn off interactive mode by default (interactive: false) at document level. Should I make a separate issue?
The text was updated successfully, but these errors were encountered:
Also, I'm learning SQL using the BigQuery emulator, hence I need all cell to produce notebook output, but it seems that there is no way to turn off interactive mode by default (interactive: false) at document level. Should I make a separate issue?
Yes, let's make a separate issue for this, please @AndhikaWB.
First of all, I'm running runme on Windows, but using Git bash as the default shell (added to PATH as well)
When I run shell commands in interactive mode, the integrated terminal is opened up and the code is executed successfully
However, I want to print the cell output to the notebook, so I turned off the interactive mode. However, it seems that the commands are now wrong, even though it executed fine previously
When checking the output tab it shows something like this
Also, I'm learning SQL using the BigQuery emulator, hence I need all cell to produce notebook output, but it seems that there is no way to turn off interactive mode by default (
interactive: false
) at document level. Should I make a separate issue?The text was updated successfully, but these errors were encountered: