From: "Ludovic Courtès" <ludo@gnu.org>
To: lloda <lloda@sarc.name>
Cc: Jeremy Phelps <jeremyphelps077@gmail.com>, 59540@debbugs.gnu.org
Subject: bug#59540: Calling length on a very long improper list is disastrous.
Date: Mon, 12 Dec 2022 12:45:08 +0100 [thread overview]
Message-ID: <87sfhk26d7.fsf@gnu.org> (raw)
In-Reply-To: <602C3A2B-D6B0-42F2-8E50-7A9E581A9879@sarc.name> (lloda@sarc.name's message of "Mon, 12 Dec 2022 10:25:39 +0100")
Hi,
lloda <lloda@sarc.name> skribis:
> I think excessive output is a more serious problem, because it should be possible to go to a backtrace frame and look at objects directly. On the other hand, it should also be possible to C-c when guile starts to flood the terminal. But neither of these workarounds is reliable :-/ Ultimately this printing should be configurable.
>
> We already have the repl-option system (repl-option-set! repl 'print ...). This system doesn't apply to exception messages nor backtraces. I think if it did, that would mostly solve the problem.
Yes. Right now it’s just $COLUMNS; we should have a documented SRFI-39
parameter for that.
> I also think that, besides options to truncate or not, we should have a pager (display at most a page, give options to next/stop/all). That would be the best default.
Yes!
Ludo’.
prev parent reply other threads:[~2022-12-12 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:52 bug#59540: Calling length on a very long improper list is disastrous Jeremy Phelps
2022-12-10 17:27 ` Ludovic Courtès
2022-12-12 9:25 ` lloda
2022-12-12 11:45 ` Ludovic Courtès [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=87sfhk26d7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59540@debbugs.gnu.org \
--cc=jeremyphelps077@gmail.com \
--cc=lloda@sarc.name \
/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).