From: <tomas@tuxteam.de>
To: 29684@debbugs.gnu.org
Subject: bug#29684: exception printers - request for improvement
Date: Wed, 4 Jul 2018 11:30:12 +0200 [thread overview]
Message-ID: <20180704093012.GA23703@tuxteam.de> (raw)
In-Reply-To: <20180703163123.0514c5aa@capac>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Jul 03, 2018 at 04:31:23PM -0300, David Pirotte wrote:
> Hi Ludovic,
>
> > > It is perfectly fine, on the opposite side, to ask advanced scheme users (who
> > > would want to, but I really don't see the point) configure guile s the repl and
> > > the exception printer so it tries to print the full content of huge lsts,
> > > vectors, arrays ...
>
> > Perhaps you could arrange to set the REPL’s ‘print’ option right from
> > one of the Guile-OpenCV modules? I mean the configuration you mention
> > have doesn’t have to be done manually by users.
>
> I'll do that yes, since I failed to convince you it you be a better default for all
> of us, not just Guile-CV :)
Hm. Applying the peanut gallery factor to my opinion (roughly 10e-7), I tend to
side with David's position: the default consumer of REPL's print is a human, and
feeding him/her with huge binary things isn't "tasty"...
But... grain of salt, and things. What would be David's position's downsides?
Thanks
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAls8k6QACgkQBcgs9XrR2kaJSgCePeZgTTphZmdrkww/uoVm/9mW
Ib4An2/NY2kWS6Oso7w9jzSP8s9x9mZz
=KsrJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-07-04 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 3:26 bug#29684: exception printers - request for improvement David Pirotte
2018-07-01 16:30 ` Ludovic Courtès
2018-07-01 22:23 ` David Pirotte
2018-07-02 6:49 ` Ludovic Courtès
2018-07-03 19:31 ` David Pirotte
2018-07-04 9:30 ` tomas [this message]
2018-08-04 2:17 ` David Pirotte
[not found] <mailman.20.1513184404.6520.bug-guile@gnu.org>
2017-12-14 14:38 ` Daniel Llorens
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=20180704093012.GA23703@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=29684@debbugs.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.
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).