From: Robert Vollmert <rob@vllmrt.net>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Can we increase the print width/column in daemon backtraces
Date: Mon, 15 Jul 2019 22:41:37 +0200 [thread overview]
Message-ID: <377F5C5B-ED9C-4D4D-9DA5-1DA30E143FD0@vllmrt.net> (raw)
In-Reply-To: <B222EDD3-8E5B-4B3F-BBD6-BA55F60EC55C@vllmrt.net>
On 15. Jul 2019, at 20:38, Robert Vollmert <rob@vllmrt.net> wrote:
>
>> On 15. Jul 2019, at 17:40, Ricardo Wurmus <rekado@elephly.net> wrote:
>>
>> P <pronaip@protonmail.com> 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.
prev parent reply other threads:[~2019-07-15 20:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 10:36 Can we increase the print width/column in daemon backtraces Pierre Neidhardt
2019-07-15 12:47 ` Ricardo Wurmus
2019-07-15 12:56 ` Pierre Neidhardt
2019-09-17 1:58 ` Maxim Cournoyer
2019-09-17 6:46 ` Pierre Neidhardt
2020-05-20 9:02 ` Pierre Neidhardt
2020-05-21 11:14 ` Katherine Cox-Buday
2020-05-22 8:14 ` Pierre Neidhardt
2020-05-24 21:19 ` Ludovic Courtès
2020-05-25 8:39 ` Pierre Neidhardt
2020-05-25 9:54 ` Tobias Geerinckx-Rice
2020-05-25 11:51 ` Pierre Neidhardt
2020-05-25 21:28 ` Ludovic Courtès
2020-05-26 7:16 ` Pierre Neidhardt
2020-05-25 11:51 ` Pierre Neidhardt
2020-05-25 15:26 ` Marius Bakke
2020-05-26 7:17 ` Pierre Neidhardt
2020-05-26 7:50 ` Marius Bakke
2020-05-26 8:19 ` Pierre Neidhardt
2020-05-27 10:43 ` Ricardo Wurmus
2020-05-27 11:09 ` Pierre Neidhardt
2020-05-28 22:07 ` Ludovic Courtès
2020-05-29 9:30 ` Pierre Neidhardt
2019-07-15 12:58 ` swedebugia
2019-07-15 15:23 ` P
2019-07-15 15:40 ` Ricardo Wurmus
2019-07-15 18:38 ` Robert Vollmert
2019-07-15 20:41 ` Robert Vollmert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=377F5C5B-ED9C-4D4D-9DA5-1DA30E143FD0@vllmrt.net \
--to=rob@vllmrt.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).