all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Mathieu Othacehe <othacehe@gnu.org>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: configurable guile backtrace in builder
Date: Thu, 09 Feb 2023 09:24:19 +0000	[thread overview]
Message-ID: <xryv5ieybeKIv5dq1oDsGt-r9EN87WQWc23yop1YTPAKfMNy_sCiOvnP6c55vOaFS8J5_MoOTyzsruV7s_ImVt-puerqXvNsZAOiFXmT2jg=@lendvai.name> (raw)
In-Reply-To: <87357gzebc.fsf@gnu.org>

> How about passing #:env-vars '(("COLUMNS" . "200")) to
> ‘gexp->derivation’ (in the build system), or adding a phase that sets
> that environment variable?


i assume printed guile backtraces should not be part of the normal output of any package.

and then why not introduce an env variable (or some other way) that only affects the backtrace, and nothing else?

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
If the source of fear is the unknown, and fear is the only way to be controlled, then knowledge is the only way to be free.



  parent reply	other threads:[~2023-02-09  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 18:19 [bug#60632] [PATCH 1/1] services: base: Add extra-env support to guix-configuration Mathieu Othacehe
2023-01-11 19:38 ` Maxim Cournoyer
2023-01-31 22:18   ` Ludovic Courtès
2023-02-01 18:31     ` configurable guile backtrace in builder (was: services: base: Add extra-env support to guix-configuration) Maxim Cournoyer
2023-02-08  9:39       ` configurable guile backtrace in builder Ludovic Courtès
2023-02-08 16:09         ` Maxim Cournoyer
2023-02-09  9:24         ` Attila Lendvai [this message]
2023-10-14 19:54     ` bug#60632: [PATCH 1/1] services: base: Add extra-env support to guix-configuration Mathieu Othacehe

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='xryv5ieybeKIv5dq1oDsGt-r9EN87WQWc23yop1YTPAKfMNy_sCiOvnP6c55vOaFS8J5_MoOTyzsruV7s_ImVt-puerqXvNsZAOiFXmT2jg=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=othacehe@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.