unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: Mike Gran <spk121@yahoo.com>, Vladimir Zhbanov <vzhbanov@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: display-backtrace
Date: Sat, 2 Mar 2019 18:36:39 +0100	[thread overview]
Message-ID: <CAJ98PDwZx+8xNa4ussqKrM7woh888NMX+YwDk5oR7CR3vnuO8w@mail.gmail.com> (raw)
In-Reply-To: <20190302160318.GA23161@spikycactus.attlocal.net>

Il giorno sab 2 mar 2019 alle ore 17:03 Mike Gran <spk121@yahoo.com> ha
scritto:

> On Sat, Mar 02, 2019 at 04:23:34PM +0100, Catonano wrote:
> > API reference -> Debugging -> Programmatic error handling
> >
> > Would you mind to let me know if you succeed in making this thing work
> for
> > you ?
> >
> > Thanks
>
> I tried (debug-set! width 1000), but, I still got a truncated
> backtrace on Guile 2.2.4
>
> (setenv "COLUMNS" "1000")
>
> did work for me, however.
>
> (use-modules (system repl debug))
> (terminal-width 1000)
>
> also worked for me.
>
> If you ever need a two-line program to test backtrace width, you can
> use
>
> (define (func x)
>   (/ 1 x))
> (map func (reverse (iota 100)))
>
> Hope this helps,
> Mike Gran
>


thank you Mike

I meant to ask to inform me about the success of this attempt to Vladimir
Zhbanov, not to you, I just mis-operated the email GUI, here


  reply	other threads:[~2019-03-02 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17  9:07 display-backtrace Vladimir Zhbanov
2019-03-01 11:46 ` display-backtrace Mike Gran
2019-03-02 15:20   ` display-backtrace Catonano
2019-03-02 15:23     ` display-backtrace Catonano
2019-03-02 16:03       ` display-backtrace Mike Gran
2019-03-02 17:36         ` Catonano [this message]
2019-03-03 14:31           ` display-backtrace Vladimir Zhbanov
2019-04-21 10:15             ` display-backtrace Vladimir Zhbanov

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=CAJ98PDwZx+8xNa4ussqKrM7woh888NMX+YwDk5oR7CR3vnuO8w@mail.gmail.com \
    --to=catonano@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=spk121@yahoo.com \
    --cc=vzhbanov@gmail.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).