Dale,

? output can not be captured as text, it's just been painted onto the underlying window.

The debug output window works the way you want. You can debugout to it on the fly.

>Both of your ideas are interesting but they do not accomplish what I am looking for. I just want the ability to copy the basic output from the "?" command. I do a LOT of UNIX like shell stuff and CMD.exe stuff and am very use to being able to copy the output of my commands, when inspired. The techniques presented don't accomplish this goal. They both seem to come from the perspective of deciding when you want to chature output and then dogin stuff to setup for that capture. I would like to not have to think about it ahead of time. I would like to just be developing and then, after the fact, decide that some of the output is valuable enough to be worth copying.
>
>It seems that since there is a Windows window with text in it there must be a way to hook in and copy it. I have been considering looking at native winAPI calls to see if there is some way to go there... I am just so use to command shells that allow copying from the output that I really miss it.