I assume the console view is virtualized and so I can't copy a large amount of output at once. This is useful when debugging the Chrome adapter since it has a setting to write tons of logs into the console.
Until you can select more than one page, could you maybe implement https://github.com/Microsoft/vscode/issues/3974 so at least the whole output could be copied at once, directly? I am also often in the position that I ask people to send me their logs and they cannot...
I believe this is fixed now in 1.8+ and can be closed out :+1: @roblourens
@MarkPieszak no, it is not fixed unfortunetly 馃悵
Oh strange maybe I was in another tab sorry! Apologies :(
https://github.com/Microsoft/vscode/commit/e261525aad152779f5fda7c253a0f62d92a529ff
Did this commit just add a "copy" item to the right click context menu? If so, that button still has this same issue. Seems to function the same as cmd/ctrl + c. If it's not feasible or easy to add a way to copy all selected text instead of only what's in the window, a "copy all" button would suffice and I can get the snippet I need in another window. But having to copy / paste in fragments is a terrible UX.
A hack of this would be redirect output to a file, what I did was to add ">" and then a filename like "output.txt" to "launch.json" in the "args" field. Works fine for now.
Is "selecting and copying a region of text" really so novel or difficult to figure out? I can swear I've seen such a thing in another app once.
@benjamin21st mind adding a quick snippet so we can see this formatting? This sounds very useful. Will it overwrite each time we run the debugger, or always add to the file?
@JacobJT Just like in command line you can do something like:
./myprogram > output.txt
In VS Code, you can set up your launch.json file such that it has the following args in one of your tasks:
"args": [
"arg1",
"arg2",
">",
"output.txt"
]
This issue is so disturbing. It basically makes the debug console useless... worse than useless actually since you need to change perfectly good reporting code just to be able to read some logs.
Would love to see this. Trying to debug some rather lengthy request body differences that would be much easier to use a diff tool on.
It would also give us a way to search the console output, which currently I am not able to figure out how to do.
This issue makes me think twice before attempting to file issues for an extension. The hack @benjamin21st mentioned does not work for me (I'm on linux)
I have investigated today for the things needed in order to make this work:
selectionchange and selectstart eventstextas we are scrolling in the tree. This can be rather tricky if the selection is changing directionsAn alternative approach is to determine on what element in the model the selection started and where it ended and to copy the content between these elements. However the issue here is that the selection will not in some cases match what is being copied.
Another alternative approach is to use the editor for the debug console implementaion which is captured here #11462
Since the ideas above require quite an effort and would introduce additional issues for now we have chosen a pragmatic solution already suggested by @felixfbecker and have added a context menu action to simply copy all the output. So keeping this issue open as a feature request to be able to do more fine grained multi page copying but pushing it to backlog as I believe this workaround will help with most scenarios.
You can try it out in tomorrows insider build or in the next stable at start of june.

Can we add a "Copy All (Unformatted)" or "Copy All (Plain text)" function to the menu?
When I copy/paste the log into text editor (like Notepad++), there are characters that editor can't display. It would be a lot easier to analyze the log if we can just copy the log as plain text.
@zhaihm please open a new issue / feature request for this and ping me on it. Thanks
Thanks for the replay. @isidorn I opened #28094 for this feature.
I am using latest version 1.13.1, I can not see Copy All. Is there any flag to enable this?

@smarigowda that is the variables panel, not the debug console
thank you. I can see it in debug console. Impressed with your lightning fast reply 馃憤
This issue also applies to less-than-multipage selections in my opinion. Select a single character in the Debug Console, scroll the Debug Console up or down just far enough that the selection disappears, then scroll back to the original scroll position - the selection is gone.
Most helpful comment
I have investigated today for the things needed in order to make this work:
selectionchangeandselectstarteventstextas we are scrolling in the tree. This can be rather tricky if the selection is changing directionsAn alternative approach is to determine on what element in the model the selection started and where it ended and to copy the content between these elements. However the issue here is that the selection will not in some cases match what is being copied.
Another alternative approach is to use the editor for the debug console implementaion which is captured here #11462
Since the ideas above require quite an effort and would introduce additional issues for now we have chosen a pragmatic solution already suggested by @felixfbecker and have added a context menu action to simply copy all the output. So keeping this issue open as a feature request to be able to do more fine grained multi page copying but pushing it to backlog as I believe this workaround will help with most scenarios.
You can try it out in tomorrows insider build or in the next stable at start of june.