From: Jose Antonio Ortega Ruiz <INVALID.NOREPLY@gnu.org>
To: Jose Antonio Ortega Ruiz <jao@gnu.org>, bug-guile@gnu.org
Subject: [bug #30904] Feature request: debugger comand to echo the error string
Date: Mon, 30 Aug 2010 03:37:06 +0000 [thread overview]
Message-ID: <20100830-033705.sv424.78785@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?30904>
Summary: Feature request: debugger comand to echo the error
string
Project: Guile
Submitted by: jao
Submitted on: Mon 30 Aug 2010 03:37:05 AM GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
When a debugging session gets long, the original error message will scroll
up, out of sight. A debugger command to show again that message would come in
handy for such cases.
Full disclosure: besides, it would simplify Geiser's handling of the
debugger.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30904>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next reply other threads:[~2010-08-30 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 3:37 Jose Antonio Ortega Ruiz [this message]
2010-08-31 11:53 ` [bug #30904] Feature request: debugger comand to echo the error string Jose Antonio Ortega Ruiz
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=20100830-033705.sv424.78785@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=jao@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).