On 09/08/2023 14:44, Ihor Radchenko wrote:
Unfortunately, I was not able to find a way to do it and yet display the error backtraces. The best we can do is using `backtrace-get-frames' in the error handler:
My version of the script prints allowed number of error messages and stack of the error that exceeds the count. I decided that it provides better balance of details. However printing at least one error stack may be better.
