When I run my program in VS2010,
because my output quite a lot,the console just discards my previous output.
For example, consider my output to be of 400 lines, lines 1 to 80 are not displayed, only lines 81 to 400 are displayed.
Any idea of how I can see the entire output?
You can change the buffering settings of the console: right click the title bar of the console window and select "Properties." On the "Layout" tab, change the "Height" of the Screen Buffer to some large number (9999, for example).
Run your program again.
Of course, if you have a large amount of output that you need to inspect on a regular basis, it's probably best to write to a file instead.
Console.BufferHeight = x;
Console.BufferWidth = x;
Sets the height and width of the console buffer.
Right before your output.
You can set it dynamically based on output but be sure to remember that if a line is longer than the width you will have additional lines to contend with.
Related
The default setting for Cmder is to wrap text output. But how to set Cmder do not wrap text output?
The Cmder, i meant : http://cmder.net/
As of now, I don't believe there is a way to disable text wrapping.
Someone did open an issue related to disabling line wrapping.
However, as featured in ConEmu's Roadmap:
Current ConEmu version allows neither horizontal scrolling nor setting horizontal buffer size.
Try running command mode, then you will see parameters below.
Status for device CON:
Lines: xxxx
Columns: xxxx
Keyboard rate: xx
Keyboard delay: x
Code page: xxx
Remember the value of Columns, just in case you want to roll it back. Now execute command mode 1000 and the Column parameter should change to 1000. (or use any higher number till you get desired result)
This also works on cmd and powershell.
I need to see output of db.currentOp() in my mongo console (mongo.exe) on Windows. But it gives so much results that they don't fit the screen. If I scroll up with the scrollbar on the left, I still can't get entire output. Is there a way to see the entire output?
Thanx
It sounds like you need to increase the Screen Buffer Size in your Windows Command Prompt settings.
I've got emacs in front of me.
I've run a find-grep, and it's got many hits, which are displayed in a window. The file names are displayed in green as hyperlinks.
I make that the only window, with C-x 1.
If I click on a file name, the window splits vertically, and the file with the found text is displayed in the other window.
If I click on further filenames, then the new file replaces the old file, which is what I want to happen.
So far, so good...
However if I resize the windows, then emacs will periodically (when I click) split one of the two windows again, rendering the display difficult to read. It will then cycle opening new files between the two new windows. Occasionally it will open more windows and make the situation worse. If I close any of these new windows they just get reopened again.
In fact sometimes this perverse behaviour happens even if I don't resize anything. It just seems to happen more often if I do.
I would like emacs to stop buggering around and just have one find-grep window and one 'display' window, and always replace the display window with the new file. I would also like to be able to set these windows to the sizes that seem most convenient.
Is there any way to achieve this?
Or can anyone point me to an essay on how the whole (replace the contents of this window/replace the contents of a different window/create another window by splitting) thing works, so I can go and hack it sane.
Short fix:
Try doing this
(setq split-height-threshold nil
split-width-threshold nil)
This will prevent Emacs from splitting windows automatically (horizontally or vertically). This might be undesirable in other situations, but this should do the job. Try it for a week or so and see if it disrupts your flow.
Also, I found that if the point was in one of the windows, and I clicked on a link, the file opened up in the next window (if any).
So, if you want to make the file open in the right window (when you have more than one window), you can ensure that the point is in the window before the window you want.
Longer answer:
OK. I was able to reproduce the problem. The thing is the window showing the files is pretty big (wide or tall) because you resized it and Emacs sees that the width or height is greater than the respective threshold and splits it likewise. So, we have to either make the threshold higher or disallow the behaviour completely.
And, just to answer the last few questions:
To get current window - (selected-window)
To get next window - (next-window)
To select a window - (select-window foo-window)
To get the buffer of the current window - (current-buffer)
To get the buffer of some window - (window-buffer foo-window)
To set a buffer for a window - (set-window-buffer foo-window bar-buffer)
I'm sure you can hack together decent window/buffer management functions using these functions.
You can use C-h f to get more details on each of these functions.
Also check out the Elisp manual - http://www.chemie.fu-berlin.de/chemnet/use/info/elisp/elisp_26.html
Is there a way to set the mac terminal to output its lastest output in a different color?
I am tired of wasting time looking for the last command when the terminal gets filled.
No, but you could arrange for your prompt to be in a different color. You could also split the pane; the bottom will scroll with the output while the top stays wherever it was.
I am doing my first steps with GDB in TUI mode.
During the debug session I see that each line outputted to console occurs in a single line (in the picture you see 222222 highlighted in red). It is like having an output pane of one single line.
On top of that, each \n doesn't cleanup that line so all the strings do overwrite each other making my output very confusing.
Can you help me a bit with this issue or point me to some key command to look for in order to have a clean output?
I also highlighted another area (in the picture 1111111) because the first string is outputted there and then all other on the frame of the source code window.
You can always refresh tui screeen every time your program outputs something with Ctrl+L key binding. Or you can temporarily swith to normal mode, step and watch program output and switch back to tui mode (Ctrl+X A). See all key bindings here.