From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 35542@debbugs.gnu.org
Subject: bug#35542: Installer does not display full backtrace on error
Date: Wed, 08 May 2019 16:35:01 +0200 [thread overview]
Message-ID: <87y33hui96.fsf@gnu.org> (raw)
In-Reply-To: <87o94i42md.fsf@gmail.com> (Mathieu Othacehe's message of "Sat, 04 May 2019 18:15:54 +0200")
Hi Mathieu,
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
> + ;; Initialize 'terminal-width' in (system repl debug)
> + ;; to a large-enough value to make backtrace more
> + ;; verbose.
> + (setenv "COLUMNS" "200")
What about instead doing something like this:
(use-modules ((system repl debug) #:select (terminal-width)))
(with-fluids ((terminal-width 200))
…)
?
That would ensure we’re only changing Guile’s notion of the terminal
width and not interfering with other tools we might launch as child
processes.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2019-05-08 14:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 8:59 bug#35542: Installer does not display full backtrace on error pelzflorian (Florian Pelz)
2019-05-03 9:40 ` Danny Milosavljevic
2019-05-03 10:09 ` Ludovic Courtès
2019-05-03 12:15 ` Mathieu Othacehe
2019-05-03 17:46 ` pelzflorian (Florian Pelz)
2019-05-04 9:43 ` Mathieu Othacehe
2019-05-04 12:24 ` pelzflorian (Florian Pelz)
2019-05-04 12:54 ` Danny Milosavljevic
2019-05-04 16:14 ` Mathieu Othacehe
2019-05-04 16:15 ` Mathieu Othacehe
2019-05-08 14:35 ` Ludovic Courtès [this message]
2019-05-14 12:09 ` Mathieu Othacehe
2019-05-14 21:02 ` Ludovic Courtès
2019-05-15 7:30 ` Mathieu Othacehe
2019-05-04 17:06 ` Danny Milosavljevic
2019-05-04 17:38 ` pelzflorian (Florian Pelz)
2019-05-04 17:40 ` pelzflorian (Florian Pelz)
2019-05-04 17:26 ` pelzflorian (Florian Pelz)
2019-05-14 16:01 ` Danny Milosavljevic
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=87y33hui96.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35542@debbugs.gnu.org \
--cc=m.othacehe@gmail.com \
/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.