You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today if an editor binding or prompt throws an exception, Elvish only shows the error message and hides the full stack trace. It should be possible to show the full stack trace.
This can be implemented by supporting a flag $edit:show-exception-stack-trace, and show the stack trace when it is true.
The text was updated successfully, but these errors were encountered:
@zzamboni Rest assured that it's being prioritized - it's part of the 0.14 milestone :)
I am considering a different way to implement this:
Add a list variable $edit:exceptions to save exceptions.
Whenever an exception happens in one of the editor callbacks, print out the index where the exception is saved (e.g. exception saved in $edit:exceptions[3])
Add a builtin to print the full exception stack trace, e.g. show-exc $edit:exceptions[3].
It also makes sense to add a exc module for exceptions utilities, so the show-exc command can be exc:show instead.
Today if an editor binding or prompt throws an exception, Elvish only shows the error message and hides the full stack trace. It should be possible to show the full stack trace.
This can be implemented by supporting a flag
$edit:show-exception-stack-trace
, and show the stack trace when it is true.The text was updated successfully, but these errors were encountered: