<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 19 Jul 2018, at 8:43, Louis Abraham wrote:</p>
</div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">It would be great to be able to see the full traceback when a command fails!</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">I looked into this, but it’s a bit complicated because currently TextMate uses the system’s error reporting (via <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">NSError</code>) so the dialog is a system dialog presented with <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">presentError:</code> which does not allow to augment it, other than add additional buttons.</p>
<p dir="auto">So one could add a “Show Error Log” button, but that does feel a bit clumsy.</p>
<p dir="auto">I do wonder though in what context you need to read the full stack dump?</p>
<p dir="auto">I ask because normally the stack dump is indicating that there is a problem with a bundle item, but a few bundle items have incomplete error handling and thus do show the stack dump in some edge cases, so I wonder if you are requesting better presentation of the stack dump because you run into these bundle items (in which case the better solution is probably to just add better error handling to the bundle items) or as a bundle developer.</p>
</div>
</div>
</body>
</html>