[BUG] While using cursive, stacktrace (on panic) are never printed to (non-alternate) screen about cursive

[gyscos]

Hi, and thanks for the report!

I think the issue is that the message is printed at the time of the panic, before unwinding (and calling drop). Then, unwinding happens, and the screen is cleared.

I see two possible workarounds:

• Redirect stderr (for example manually to a file with 2> err - fine for development, not ideal user experience
• Override the panic handler, save the message/backtrace, and print it after unwindinging. Haven't fully checked how feasible that is, but it might make things more seamless.
  One problem is that "after clearing the screen" is currently in the drop implementation of the runner. I guess we could re-raise the panic there?