[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can we increase the print width/column in daemon backtraces
From: |
Robert Vollmert |
Subject: |
Re: Can we increase the print width/column in daemon backtraces |
Date: |
Mon, 15 Jul 2019 22:41:37 +0200 |
On 15. Jul 2019, at 20:38, Robert Vollmert <address@hidden> wrote:
>
>> On 15. Jul 2019, at 17:40, Ricardo Wurmus <address@hidden> wrote:
>>
>> P <address@hidden> writes:
>>
>>>> Hi Pierre,
>>>>
>>>>> Quite often when packaging and iterating, the daemon produces backtraces
>>>>> on errors, which could be very useful to understand what's wrong, but
>>>>> unfortunately the output is truncated to some 80-ish column.
>>>>
>>>> Set the COLUMNS environment variable to some large value.
>>>>
>>> Can't it just not truncate them? This is a very brutish way of
>>> condensing log output and breaks some workflows.
>>
>> I also don’t like it, but that’s what Guile does. (It’s not Guix that
>> truncates the output.)
>
> It’s open source, though, isn’t it? Let’s fix it!
I sent a patch against guile:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36677
If you’d like to try it in guix, here’s a patch to apply the patch to
guile-next,
though I guess to make it apply to the build daemon you’d have to apply it to
gnu/packages/guile.scm:guile/fixed.
Happy to submit a patch to do that.