See http://support.microsoft.com/kb/99115, “INFO: Preventing the Console Window from Disappearing”. The idea is to use GetConsoleScreenBufferInfo to determine that the cursor has not moved from the initial 0,0 position. Code sample from @tomlogic, based on the referenced Knowledge Base article: // call in main() before printing to stdout // returns TRUE if program is in its …
A quick Google revealed a thread on Coderanch which was useful. There are several other ways of doing console writing but there seems to be no real benefit of using one or the other apart from less code to write and that the creation of a new PrintWriter object will take up more memory (eventually). …
This is standard behavior in the Groovy shell, not peculiar to the Grails shell. You probably don’t want to def the variable. See the following: ~ $ groovysh Groovy Shell (2.3.4, JVM: 1.7.0_45) Type ‘:help’ or ‘:h’ for help. ——————————————————————————- groovy:000> def x = 42 ===> 42 groovy:000> x Unknown property: x groovy:000> y = …
Just press c. It will continue execution until the next breakpoint. You can also disable intermediate breakpoints by using disable #breakpointnumber as stated here.
The list found at http://msdn.microsoft.com/en-us/library/system.console.backgroundcolor.aspx I believe are the only supported colors in console. No hex allowed. Black DarkBlue DarkGreen DarkCyan DarkRed DarkMagenta DarkYellow Gray DarkGray Blue Green Cyan Red Magenta Yellow White EDIT Get the working project files off my public Repo https://bitbucket.org/benskolnick/color-console/ But on further investigation you can do a lot of work …
If you just need a quick, temporary size bump you can press Ctrl + / – to zoom and Ctrl 0 to reset.
In my case, all console messages were not showing because I had left a string in the “filter” textbox. Remove the filter it by clicking the X as shown:
They are completely equivalent when used with printf(). Personally, I prefer %d. It’s used more often (should I say “it’s the idiomatic conversion specifier for int“?). (One difference between %i and %d is that when used with scanf(), then %d always expects a decimal integer, whereas %i recognizes the 0 and 0x prefixes as octal …
How about std::cin.get(); ? Also, if you’re using Visual Studio, you can run without debugging (CTRL-F5 by default) and it won’t close the console at the end. If you run it with debugging, you could always put a breakpoint at the closing brace of main().