From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@igalia.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 29669@debbugs.gnu.org
Subject: bug#29669: repl-print - requet for iprovement
Date: Fri, 3 Aug 2018 23:37:03 -0300 [thread overview]
Message-ID: <20180803233703.6bdc69e3@capac> (raw)
In-Reply-To: <87po02jf67.fsf@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
Hi Ludo,
Andy,
> > 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
> > # …)
> >
> > So the question becomes: should we change the default?
Why not? then who would want multi-line prints would do the 'oppoite' of the above,
right?
scheme@(guile-user)> ,use (ice-9 pretty-print)
scheme@(guile-user)> ,o print (lambda (repl obj) (write obj) (newline))
Or, as I do in Guile-CV, implement a specific display method for 'their
objects' (im-display in guile-cv, and the manual says 'to be used with caution...)
> > I have a slight preference for keeping the default as it is to avoid
> > surprises, but no strong opinion.
What surprise(s)? :),
I mean, what sort of code or who's the one of us who would rely on the repl print
'layout' in any sort of way(s)?
> > Andy, Mark, others, WDYT?
> Hoo, I don't know. If we were to do this it should be controllable by
> REPL options, I think; we'd need the ability to go back and forth. But
> if we have the option I think it could make sense for it to be on by
> default, like what GDB does.
It seems to me it is a yes :)
note that (just not to forgot), we need this to be done both for the repl
_and_ exception printers as well ... it is as essential if not more then
within the repl
> Thing is, truncated-print does its job only OK, not great, so it's a hard sell to
> standardize on it. You probably do want multi-line prints sometimes...
I'm actually using truncated-print all the time, since it is simply impossible
otherwise to use/develop guile-v, and I never spotted any 'problem' (not to say I
can guarantee there is none of course, but that did not happen in years). Then we
could always improve when someone report a problem ...
Thanks,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-08-04 2:37 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
2018-07-05 7:49 ` Andy Wingo
2018-08-04 2:37 ` David Pirotte [this message]
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=20180803233703.6bdc69e3@capac \
--to=david@altosw.be \
--cc=29669@debbugs.gnu.org \
--cc=ludo@gnu.org \
--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).