I’m using the latest public build and when I quit the Corona Simulator the terminal screen that it starts, closes like it should. For people using Glider, you can disable the terminal by running this command:
defaults write com.coronalabs.Corona_Simulator no-console -bool true
I’m seeing every expected message in the terminal.
I am using Corona plugin for sublime text. I am SO happy to have the new terminal disabled. Thanks for posting about it. So many windows to close before…
We’re using IntelliJ and the console/terminal’s not responding at all.
For the people programming Corona, you can add a button that does:defaults write com.coronalabs.Corona_Simulator no-console -bool true
So it becomes optional, and easy to find.
Sorry, but this is not just Glider, there are other editors that have this problem as well.
The option should have been tested a bit better. But that is why it is a daily build right? so these type of things can get resolved?
+1
Using command line without formal documentation to disable the console window is kind of odd.
+1 for disabling the automatic console through the preferences and restoring some way to output to the current terminal (like Corona Terminal used to do). I had aliased ‘corona’ to Corona Terminal, then I could just use ‘corona .’, but now I can either open my project graphically or use the long ‘open -a’ command. And ‘open -a’ doesn’t output to the current terminal. Neither does the no-console setting; it just suppresses output.
It feels far more natural for me to use the same workflow with all my projects (open terminal, ‘cd directory’; ‘clang main.c’ and open terminal, ‘cd directory’; ‘node main.js’ and open terminal, ‘cd directory’; ‘corona .’, etc.) than to use one workflow with my C, C++, JS, and other languages’ projects and a different one with Corona.
+1 for fixing new “console” behaviour somehow (on mac)
after switching to new in new daily builds, new console output doesn’t update or show any output most of the time. i realised this is somehow linked to OS X console.app that doesn’t update itself automatically (i need to click “reload” to refresh logs). on second mac it works “ok”, but prints everything with delay and in chunks so it is impossible to correlate "print"s to in-game events (probably also linked to console.app refresh time)
it’s impossible to do any work w/o debug output.
The idea before was you were supposed to run Corona Terminal, which ran Corona Simulator and it wrote its output to STDOUT (i.e. the Terminal window that ran Simulator. Messages showing up in the Console.app were probably STDERR messages or perhaps we were forking them to both places. But the intent was to have a Terminal.app running where the output shows up.
On Windows, running Corona Simulator creates the CMD windows for you. This is desirable for most people because they can now make shortcuts, i.e. the Doc directly from Corona Simulator and get the Terminal window where output goes fired up for you. No need for the script to do it the other way.
Of course, there are people who need to bypass this behavior, like getting it to open from another program and that forking of the program captures the STDOUT content to the parent so programs see it, not a terminal window. We provided a command to turn off the terminal for those who don’t want it.
Because you can use the “open” command, in your case Caleb, why not create a shell script and drop it in your bin directory called “corona”
#!/bin/bash
open -a /Applications/CoronaSDK/Corona\ Simulator.app/ $1
Then do a:
chmod a+x corona
@peter.janosik, the terminal window we open shows output identical to when you ran Corona Terminal and saw the output there. Corona has always buffered this output. You can add this line to the top of your main.lua to turn off the buffering:
io.output():setvbuf(‘no’)
Rob
How to open multiple simulators after this change (Mac)?
@Rob Miracle:
open -a /Applications/CoronaSDK/Corona\ Simulator.app doesn’t send the output to the current terminal. It just opens the simulator and the simulator’s console window.
The simulator’s “console window” is it’s terminal window. Why do you need it to go the terminal window you ran “open” from?
Rob
What do I have to start where to see error messages now?
@Rob Miracle:
Because I’m lazy 
Seriously, though, it just makes a slightly jarring “jump” - I prefer navigating through the terminal to get projects ready, run them, or Git-commit them, and, like I said, when I can do it with “big” things like JavaScript, C, C++, website build scripts, or raw Lua, “small” things like LESS, Stylus, shell scripts, and Git, but not with Corona, it just doesn’t seem quite “right”.
That is:
[lua]
node main.js
clang main.c
ruby main.rb
python main.py
lua main.lua
lessc file.less
stylus file.styl
./script.sh
git commit -m “Git commit”
Corona icon > open project > drag terminal to tabs
vs
corona main.lua
[/lua]
The new console is a terminal, but it requires graphical interaction - slight, but “flow breaking” - to get it set up. For someone (like me) who uses a LOT of keyboard - cmd+space > term > enter > cd project > corona main.lua > cmd+tab > text editor - a program that used to be able to work just like all the others but now requires extra clicking and dragging makes a break in my routine.
You could even just embed the Corona Terminal executable in the Corona Simulator.app package, and I’d be fine with it, if you don’t want it in the CoronaSDK folder. I’d just like some way to have access to the old way.
I’m in the same boat as you.
What I have done so far is just copy Corona Terminal from an older version. Then drop this copy into the folder that contains the latest version of CoronaSDK. I have my old way of working back, but there’s no guarantee that this will continue to work with future versions.
I have my own preferences for background color, font color and font size. That’s another reason I want the output to go the terminal of my choosing.
Based on what I’ve seen posted on this subject, a lot of us Mac user don’t care about being compatible with Windows. We want CoronaSDK on Mac to be compatible with previous versions of CoronaSDK on Mac.
For those who want Corona Terminal back, here is a shell script you can drop into a folder that’s in your $PATH. It’s best to create a bin folder in your home directory and add it to your path if you don’t already have it:
mkdir ~/bin
echo “export PATH=$PATH:$HOME/bin” >> ~/.bash_profile
and drop this script in there. Note its CoronaTerminal and not Corona Terminal. Make sure to do a:
chmod a+x ~/bin/CoronaTerminal
after creating the file.
#!/bin/bash
DEFAULT_INSTALL="/Applications/CoronaSDK"
INSTALL_DIR=$(dirname “$0”)
if [[-f “${INSTALL_DIR}/Corona Simulator.app/Contents/MacOS/Corona Simulator”]]
then
CORONA_SIMULATOR="${INSTALL_DIR}/Corona Simulator.app/Contents/MacOS/Corona Simulator"
else
CORONA_SIMULATOR="${DEFAULT_INSTALL}/Corona Simulator.app/Contents/MacOS/Corona Simulator"
fi
if [[-f “${CORONA_SIMULATOR}”]]
then
echo “Running: ‘${CORONA_SIMULATOR}’ -no-console YES $@”
“${CORONA_SIMULATOR}” -no-console YES “$@”
else
echo “ERROR: Could not find ‘Corona Simulator.app’ in ‘${INSTALL_DIR}’ or ‘${DEFAULT_INSTALL}’”
exit 1
fi
And you should be back in the Corona Terminal business. Danielle, if you run Corona Simulator, it should automatically start a terminal window for you with the output.
Thanks to Perry for working this out.
Rob
@Rob,
Thanks for the script.
When I run this, it opens up the Corona Simulator GUI. I removed the “-no-console YES” so that lines nows looks like this:
“${CORONA_SIMULATOR}” “$@”
And it starts the project running in the simulator without the GUI and the output goes to the terminal where I ran the command.
Spoke to soon. Please ignore my previous post. That change does not work as I said it would.
When I run it, I get the main menu and clicking on a project runs the simulator as expected. Try doing a SHIFT-CMD-1 to bring the welcome window that you would expect.
Rob
When starting from the command line and providing the path to the project you want to run, is there a way auto hide the welcome window?
Under preferences, I tried unchecking “Automatically open Welcome Window”. That didn’t have any impact, the welcome window always opens.
@Rob Miracle:
Great! The script works for me. I’ll have to remember about the raw executable in each app’s package next time this happens with something…
Thanks!