unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: backing out of debugger
Date: Tue, 14 Sep 2021 15:55:59 +0200	[thread overview]
Message-ID: <20210914135559.GA14713@tuxteam.de> (raw)
In-Reply-To: <CAOcxjM5d=4PyTp-OvuN+CLcGTKL4RFm1vV85MvdzWEG24Zz_bA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

On Tue, Sep 14, 2021 at 08:50:03AM -0400, Mortimer Cladwell wrote:
> Hi,
> Let's say I made a lot of mistakes. I look at my repl and see:
> scheme@(guile-user) [10]>
> 
> Any way to back out to scheme@(guile-user)> without typing ,q ten times?

Guile tells you :)

  scheme@(guile-user)> foo
  ;;; <stdin>:7:0: warning: possibly unbound variable `foo'
  ice-9/boot-9.scm:1685:16: In procedure raise-exception:
  Unbound variable: foo
  
  Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.

This [1] thingy coming next is the new prompt. So typing ,q gets me out
of it:

  scheme@(guile-user) [1]> ,q
  scheme@(guile-user)>

I'm not deep into that, but as far as I understand, the job of this
prompt is to keep information around about what went wrong, so you
can inspect it (e.g. with ,bt).

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2021-09-14 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 12:50 backing out of debugger Mortimer Cladwell
2021-09-14 13:11 ` Luis Felipe
2021-09-14 13:27   ` Mortimer Cladwell
2021-09-14 14:08     ` Luis Felipe
2021-09-14 14:35       ` Olivier Dion via General Guile related discussions
2021-09-15 15:40         ` Mortimer Cladwell
2021-09-14 13:55 ` tomas [this message]
2021-09-15 12:49 ` Matt Wette
2021-09-15 12:50   ` Matt Wette

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=20210914135559.GA14713@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=guile-user@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).