From: Mike Gran <spk121@yahoo.com>
To: Andy Wingo <wingo@pobox.com>, "guile-user@gnu.org" <guile-user@gnu.org>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Thu, 23 Feb 2017 20:04:26 +0000 (UTC) [thread overview]
Message-ID: <1253648402.3519089.1487880266545@mail.yahoo.com> (raw)
In-Reply-To: <87tw7kviu6.fsf@pobox.com>
On Thursday, February 23, 2017 11:15 AM, Andy Wingo <wingo@pobox.com> wrote:
> So! Release blockers.
I know you're asking about how to wrap up 2.2, and here
I am to suggest new features. So rude. ;-)
If I had to come up with my own personal lists of features
I'd love to claim for a future release.
* A string encoding that can handle raw bytes
to make Guile more Emacs friendly, as per many e-mails in this
thread.
http://lists.gnu.org/archive/html/guile-user/2017-02/msg00118.html
* 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.
* Fix GDB support.
From my understanding of Guile internals, the former is
tractable.
-Mike
next prev parent reply other threads:[~2017-02-23 20:04 UTC|newest]
Thread overview: 21+ 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-18 14:34 ` GNU Guile 2.1.7 released (beta), SOCK_NONBLOCK Matt Wette
2017-02-21 20:58 ` Andy Wingo
2017-02-18 17:40 ` GNU Guile 2.1.7 released (beta) Matt Wette
2017-02-18 17:48 ` Matt Wette
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04 ` Mike Gran [this message]
2017-02-23 21:06 ` Andy Wingo
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-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=1253648402.3519089.1487880266545@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.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).