So I downloaded VS2013 with the babelua plugin. Everything works perfect, but when debugging my code it opens the lua.exe command window and closes it immediately after executing it.
I have a test.lua file with a print("hello") statement in it. I can see the printed output for 0.5 secs and then the command window gets closed immediately.
Is there any way I can fix this?
Related
I'm running my code in the external Terminal. When I get to the end of my program, the Terminal automatically closes.
Is there a way to keep it open, like the "pause" command on Windows?
Working on Windows as well
Thanks for the help
On my Ubuntu (20.04) machine I have a bash script that runs firefox automatically (helps me practice bash and using the terminal). It works fine but whenever I run the command from the terminal and the window opens I inevitably get the same log message outputted to the terminal over and over again:
###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
I've looked into the message and it seems to be a common firefox error. I'm just wondering if anyone has any quick fixes for preventing it from being printed to the terminal over and over again?
The code for the script can be found here.
Thanks!
Orbital
I just started using opencv 2.4.0. So after installing, I tried to copy a sample code from here to my project. So click on F5 then a cmd screen opens then closes immediately. I tried googling but didnt find a solution. What am I doing wrong?
Go cmd, and go exe's directory, but before find a video file, copy it to that working directory too.
cd WhereYourApplicationExe
yourapplication.exe avideofile.wmv avideofile.wmv 10 1
Since it's a console application, you can either add
cin.get();
return 0;
in your Main block. This ensures that the prompt window will wait for user input before closing as, at the moment, the code is executed and the command prompt window is closed upon completion.
Alternatively, if you don't need the debugger, you can press CTRL + F5 to run it.
I'm making a application in python from Windows. When I run it in the console, it stops, shows an error, and closes. I can't see the error becase its too fast, and I can't read it. I'm editing the code with IDLE (the program that came with python when I instaled it), and when I run it with the python shell, there are no errors. I would run it from IDLE, but when I use the console, it has more features.
I don't know why this is happening. I need your help.
Run the program from an already-open terminal. Open a command prompt and type:
python myscript.py
For that to work you need the python executable in your path. Just check on how to edit environment variables on windows, and add C:\PYTHON26 (or whatever directory you installed python to).When the program ends, it'll drop you back to the CMD windows prompt instead of closing the window.Add code to wait at the end of your script. Adding ...
raw_input()
... at the end of the script makes it wait for the ENTER key. That method is annoying because you have to modify the script, and have to remember removing it when you're done.
Run your program from a Windows command prompt. That will not automatically close when the program finishes.
If you run your program by double-clicking on the .py file icon, then Windows will close the window when your program finishes (whether it was successful or not).
Create a text file in the program directory i.e. wherever your script is located. Change the extension to .bat for example text.bat. Then edit the text file and write:
python main.exe
pause
Now you can run the program without typing into the command console by double clicking the bat file, and the console window will not close.
I'm running Windows 7 and am trying to run nosetests.
It's been installed and I can run it successfully, except that when I do run it (by typing 'nosetests' in the cmd window), it'll open a new cmd window with the output - but this window closes before I can see what it says. How do I prevent the results from closing so I can see them?
I'm a real n00b, in case you hadn't noticed.