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 am using godot-rust, and I need the standard output and error for debugging purposes of my code, so I followed the command line installation documentation and installed godot through scoop. The problem is, every time I run the command, nothing gets printed, and I am able to execute other commands. I talked about it in the godot-rust server and it seems likely that the scoop intallation might be running godot on the background, but it should be in the foreground, since I believe it is more useful to be able to see the output than, just not.
I have opened an issue in scoop's extras bucket to get this changed, since for all intents and purposes, if you run it from the command line being able to see what's happening in the command line as opposed to the editor (specially when not using the editor) should be the most useful, right?
Tested versions
System information
Windows 10
Issue description
I am using godot-rust, and I need the standard output and error for debugging purposes of my code, so I followed the command line installation documentation and installed godot through scoop. The problem is, every time I run the command, nothing gets printed, and I am able to execute other commands. I talked about it in the godot-rust server and it seems likely that the scoop intallation might be running godot on the background, but it should be in the foreground, since I believe it is more useful to be able to see the output than, just not.
Steps to reproduce
Install Scoop:
Add bucket extras:
Install godot:
Run godot:
Minimal reproduction project (MRP)
No project is necessary.
The text was updated successfully, but these errors were encountered: