From: Mike Gran <INVALID.NOREPLY@gnu.org>
To: Mike Gran <spk121@yahoo.com>, bug-guile@gnu.org
Subject: [bug #31293] [HEAD] repl debugger "expected a positive width" error
Date: Mon, 08 Nov 2010 17:28:51 +0000 [thread overview]
Message-ID: <20101108-172851.sv73118.70210@savannah.gnu.org> (raw)
In-Reply-To: <20101010-160341.sv73118.1133@savannah.gnu.org>
Update of bug #31293 (project guile):
Status: None => Fixed
Assigned to: None => mike121
_______________________________________________________
Follow-up Comment #1:
I found a workaround which I pushed to git as
"pretty-print print-sequence width error"
bf61ca33025b8d75f72c41059e9f168a62d71a8f
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31293>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2010-11-08 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 16:03 [bug #31293] [HEAD] repl debugger "expected a positive width" error Mike Gran
2010-11-08 17:28 ` Mike Gran [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=20101108-172851.sv73118.70210@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@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).