call traceback is indecipherable garbage

[bauss]

On Monday, 31 January 2022 at 09:42:27 UTC, forkit wrote:
> On Monday, 31 January 2022 at 08:56:17 UTC, FeepingCreature 
> wrote:
>>
>> I think this is not a good idea. This sounds like the sort of 
>> environment variable that you usually, when it matters, want 
>> to *have set* a while ago, rather than set that moment. It's 
>> just one more "gotcha that you just need to know to work with 
>> the language."
>
> so that 'gotcha' is easily solved.
>
> when an error is printed, on the next line it could say this:
>
> =========================
>
> std.exception.ErrnoException at std\stdio.d(545): Cannot open file 
> `nosuchfile' in mode `rb' (No such file or directory)
>
> ------------------------------------------------------------------
> To see stack backtrace, set evironment variable: 
> DLANG_BACKTRACE=1
>
>
> =============================================

I would much rather that you disable stacktraces rather than 
enables them.

I have systems running for months without being able to just 
rerun on the fly when it fails.

Without a stacktrace that would fail and I most definitely 
wouldn't remember to enable that for every program I run.