From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Can we increase the print width/column in daemon backtraces Date: Mon, 15 Jul 2019 17:40:05 +0200 Message-ID: <877e8ji9wq.fsf@elephly.net> References: <87tvbn7ff3.fsf@ambrevar.xyz> <87k1cjihvm.fsf@elephly.net> <9tPianBRksiYE23D5cEQSqawK0Ryj6_jMholZe9j0Y3mF6lxzAjtO4qI033RSomrDyHILwQvCfc1WRG2SR9fT9EGRTm_k3_7gEgiEsMN8j8=@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:51640) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hn35S-0006lb-JU for guix-devel@gnu.org; Mon, 15 Jul 2019 11:40:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hn35R-00033n-Ck for guix-devel@gnu.org; Mon, 15 Jul 2019 11:40:22 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21227) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hn35R-00032o-0p for guix-devel@gnu.org; Mon, 15 Jul 2019 11:40:21 -0400 In-reply-to: <9tPianBRksiYE23D5cEQSqawK0Ryj6_jMholZe9j0Y3mF6lxzAjtO4qI033RSomrDyHILwQvCfc1WRG2SR9fT9EGRTm_k3_7gEgiEsMN8j8=@protonmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: P Cc: "guix-devel@gnu.org" P writes: >> Hi Pierre, >> >> > Quite often when packaging and iterating, the daemon produces backtrac= es >> > 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=E2=80=99t like it, but that=E2=80=99s what Guile does. (It=E2= =80=99s not Guix that truncates the output.) > I for one often use > Acme because I can just right click on paths in it and it opens them > with the plumber. If a path is split across lines, Acme can't pick > that up. Same here with Emacs (M-x ffap). -- Ricardo