From: swedebugia <swedebugia@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>,
Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Can we increase the print width/column in daemon backtraces
Date: Mon, 15 Jul 2019 14:58:16 +0200 [thread overview]
Message-ID: <97eb3df2-733f-baff-6657-03b3c057f654@riseup.net> (raw)
In-Reply-To: <87k1cjihvm.fsf@elephly.net>
On 2019-07-15 14:47, Ricardo Wurmus wrote:
>
> 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.
This should be added to the manual I think.
--
Cheers
Swedebugia
next prev parent reply other threads:[~2019-07-15 12:58 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 [this message]
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
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=97eb3df2-733f-baff-6657-03b3c057f654@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=rekado@elephly.net \
/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).