From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Thu, 23 Feb 2017 22:06:30 +0100 [thread overview]
Message-ID: <87h93kvcq1.fsf@pobox.com> (raw)
In-Reply-To: <1253648402.3519089.1487880266545@mail.yahoo.com> (Mike Gran's message of "Thu, 23 Feb 2017 20:04:26 +0000 (UTC)")
Hi :)
On Thu 23 Feb 2017 21:04, Mike Gran <spk121@yahoo.com> writes:
> I know you're asking about how to wrap up 2.2, and here
> I am to suggest new features. So rude. ;-)
Hehe :) The suggestions are still welcome. If they make 2.2.0, super!
If they make 2.2.1, also super :)
> * A string encoding that can handle raw bytes
> to make Guile more Emacs friendly, as per many e-mails in this
> thread.
I haven't digested the thread so I defer to you for the moment :)
> * Some helper funcs for debugging. For example, I just found
> out (after a decade) that Guile comes with its own pk. Also,
> a "break REPL here when condition is true" procedure would
> be great. I've sometimes rolled my own with ",break acos" and
> adding (acos 0.0) for the location in question.
Yeah pk is nice!!!! It is how I do a lot of my debugging. Silly.
The "break when condition is true" thing is totally doable.
> * Fix GDB support.
I wasn't aware that it was broken but I don't doubt it :)
Cheers,
Andy
next prev parent reply other threads:[~2017-02-23 21:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 10:31 GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04 ` Mike Gran
2017-02-23 21:06 ` Andy Wingo [this message]
2017-03-01 13:01 ` Thien-Thi Nguyen
2017-03-01 17:36 ` Andy Wingo
2017-03-02 5:50 ` Thien-Thi Nguyen
2017-02-24 0:52 ` Break-when [was GNU Guile 2.1.7 released (beta)] Matt Wette
2017-02-24 14:02 ` GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-24 17:46 ` Arne Babenhauserheide
2017-02-26 17:57 ` Andy Wingo
2017-02-27 19:32 ` Mike Gran
2017-02-27 20:30 ` Andy Wingo
2017-02-27 23:00 ` Thomas Morley
2017-02-28 8:31 ` Andy Wingo
2017-02-28 9:38 ` David Kastrup
2017-02-28 14:03 ` Andy Wingo
2017-03-05 16:54 ` Thomas Morley
2017-03-01 18:04 ` Arne Babenhauserheide
2017-02-28 0:04 ` David Pirotte
2017-02-28 1:49 ` Daniel Llorens
2017-03-02 20:54 ` David Pirotte
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=87h93kvcq1.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).