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
I like what you're doing here. Always thought the backtrace could be made more useful. It occurs to me that it can be hard to decide what exactly one should show in a backtrace, you never know what the developer wants to see, and providing everything can be an overload. That led to to think it would be cool if the backtrace did provide everything, but in YAML, and then we could pipe that to a filter command to see it in different ways, even write our own filters. We might have somthing like:
I like what you're doing here. Always thought the backtrace could be made more useful. It occurs to me that it can be hard to decide what exactly one should show in a backtrace, you never know what the developer wants to see, and providing everything can be an overload. That led to to think it would be cool if the backtrace did provide everything, but in YAML, and then we could pipe that to a filter command to see it in different ways, even write our own filters. We might have somthing like:
ruby -rbacktracer myscript.rb 2>&1 | backtracer -i locals
The text was updated successfully, but these errors were encountered: