unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Set debug output width in REPL
Date: Mon, 21 Feb 2011 11:12:24 -0500	[thread overview]
Message-ID: <871v31z7rr.fsf@netris.org> (raw)
In-Reply-To: <475017.40217.qm@web37908.mail.mud.yahoo.com> (Mike Gran's message of "Sun, 20 Feb 2011 22:02:13 -0800 (PST)")

Mike Gran <spk121@yahoo.com> writes:
> I find that the backtrace output in the REPL is too constrained
> my verbose code.  The attached patch would let one set the 
> width of the backtrace and locals meta-commands.

> index d4b3e4a..40d720d 100644
> --- a/module/system/repl/command.scm
> +++ b/module/system/repl/command.scm
> @@ -71,6 +71,8 @@
>  (define *show-table*
>    '((show (warranty w) (copying c) (version v))))
>  
> +(define *width* 72)
> +
>  (define (group-name g) (car g))
>  (define (group-commands g) (cdr g))

> What do you think?

It seems to me that *width* should not be a global variable, but rather
a per-repl setting.  It probably belongs in the options field of the
<repl> record, no?  See "repl-default-options" in repl/common.scm.

    Thanks,
      Mark



  reply	other threads:[~2011-02-21 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21  6:02 Set debug output width in REPL Mike Gran
2011-02-21 16:12 ` Mark H Weaver [this message]
2011-02-21 16:36   ` Mark H Weaver
2011-03-04 10:17 ` Andy Wingo
2011-03-05 13:26   ` Ludovic Courtès
2011-03-05 19:01     ` Andy Wingo
  -- strict thread matches above, loose matches on Subject: below --
2011-02-21 22:55 Mike Gran
2011-02-24 23:28 ` Ludovic Courtès
2011-02-26  9:17   ` Mark H Weaver
2011-03-05 19:18   ` Mark H Weaver
2011-02-25  1:43 Mike Gran

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=871v31z7rr.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=spk121@yahoo.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).