|
in reply to Re: Saving STDERR and displaying it later
in thread Saving STDERR and displaying it later
Wouldn't that just cause output to STDERR to appear immediately? The problem is, any output to STDERR or STDOUT is lost while in curses mode, and curses mode is only left when my Curses::Application object is destroyed. A solution where output to STDERR is 'held' in the buffer indefinitely until allowed to leave (after the DESTROY method is called on the Curses::Application object) would do the trick.
|
