Most times, code reloading errors come from a 'silly' mistake that doesn't deserve much stacktrace inspection.
So, in addition to the displayed stacktrace, we could present the gist of the problem as a red overlay, similar to what we've done in recent times.
While we're there, we could add defcustoms controlling both widgets (overlay, stacktrace)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4