Hi,
It would be great to be able to see the full traceback when a command fails!
best, Louis
On 19 Jul 2018, at 8:43, Louis Abraham wrote:
It would be great to be able to see the full traceback when a command fails!
I looked into this, but it’s a bit complicated because currently TextMate uses the system’s error reporting (via `NSError`) so the dialog is a system dialog presented with `presentError:` which does not allow to augment it, other than add additional buttons.
So one could add a “Show Error Log” button, but that does feel a bit clumsy.
I do wonder though in what context you need to read the full stack dump?
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.
Hi Allan,
On 21. Aug 2018, at 09:07, Allan Odgaard mailinglist@textmate.org wrote:
On 19 Jul 2018, at 8:43, Louis Abraham wrote:
It would be great to be able to see the full traceback when a command fails!
I looked into this, but it’s a bit complicated because currently TextMate uses the system’s error reporting (via NSError) so the dialog is a system dialog presented with presentError: which does not allow to augment it, other than add additional buttons.
So one could add a “Show Error Log” button, but that does feel a bit clumsy.
I see.
I do wonder though in what context you need to read the full stack dump?
For me I also bump into this issue if I run an erroneous Python script with a long error traceback.
Maybe an option would be to be able to just copy the entire output of that window(?)
Cheers, Hans
Thank you a lot for your attention.
I do wonder though in what context you need to read the full stack dump?
For me I also bump into this issue if I run an erroneous Python script with a long error traceback.
I also have issues debugging some Python bundles (as a bundle developer), but I cannot remember exactly what my issue was (maybe with python-jedi).
So one could add a “Show Error Log” button, but that does feel a bit clumsy.
I would be very happy with a temp log file or a new TextMate buffer (which is about equivalent in term of code).
Best, Louis
On 21 Aug 2018, at 9:39, mail@bibiko.de wrote:
I do wonder though in what context you need to read the full stack dump?
For me I also bump into this issue if I run an erroneous Python script with a long error traceback.
Maybe an option would be to be able to just copy the entire output of that window(?)
I have now limited output to 7 lines with a button to open the full message in a new window: https://github.com/textmate/textmate/commit/5f2e0dac286340fa0a10f8906a0ef851...
-
Allan Odgaard -
Louis Abraham -
mail＠bibiko.de