From: ludo@gnu.org (Ludovic Courtès)
To: David Pirotte <david@altosw.be>
Cc: Andy Wingo <wingo@igalia.com>, 29669@debbugs.gnu.org
Subject: bug#29669: repl-print - requet for iprovement
Date: Sun, 01 Jul 2018 18:26:37 +0200 [thread overview]
Message-ID: <87r2kmrkg2.fsf@gnu.org> (raw)
In-Reply-To: <20171211213615.7bca6fc8@capac> (David Pirotte's message of "Mon, 11 Dec 2017 21:36:15 -0200")
Hello,
David Pirotte <david@altosw.be> skribis:
> From d920d22efe3e77d23004122e21cec420c402f531 Mon Sep 17 00:00:00 2001
> From: David Pirotte <david@altosw.be>
> Date: Mon, 11 Dec 2017 21:28:24 -0200
> Subject: [PATCH] Updating repl-print to use truncated-print
>
> * module/system/repl/common.scm (repl-print): Use (truncated-print val),
> not (write val). With this update, repl-print becomes 'friendly' wrt
> large (huge) lists, arrays, srfi-4 butevoectors ...
Note that it’s already possible to do this:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use (ice-9 pretty-print)
scheme@(guile-user)> ,o print (lambda (repl obj) (truncated-print obj) (newline))
scheme@(guile-user)> (iota 500)
$20 = (0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 # …)
--8<---------------cut here---------------end--------------->8---
So the question becomes: should we change the default?
I have a slight preference for keeping the default as it is to avoid
surprises, but no strong opinion.
Andy, Mark, others, WDYT?
Ludo’.
next prev parent reply other threads:[~2018-07-01 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 23:36 bug#29669: repl-print - requet for iprovement David Pirotte
2018-07-01 16:26 ` Ludovic Courtès [this message]
2018-07-05 7:49 ` Andy Wingo
2018-08-04 2:37 ` David Pirotte
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2kmrkg2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29669@debbugs.gnu.org \
--cc=david@altosw.be \
--cc=wingo@igalia.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.
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).