From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-devel <guile-devel@gnu.org>
Subject: What is needed in guildhall to include it in Guile?
Date: Mon, 22 Feb 2016 16:08:43 +0100 [thread overview]
Message-ID: <87h9h01yr4.fsf@web.de> (raw)
Hi,
In january there was a thread here about Guildhall with the notion
> I encourage you to hack on Guildhall to make it more usable for your
> needs.
I finished my PhD last month, so I have some freed-up time — and I would
like to use some of it to hack on Guildhall and make it ready for
inclusion in Guile.
However there’s one stumbling block: I don’t see what’s actually missing
from it. So I want to be bold and request something:
Please tell me what’s missing in Guildhall, so I can implement it.
Best wishes,
Arne
[1]: https://lists.gnu.org/archive/html/guile-devel/2016-01/msg00010.html
PS: I write now, because I just stumbled over a situation again, where
I’d have loved to just have guildhall at hand by default. I wanted
to test uptop.scm which needs guile-ssh, so I just wanted to quickly
get guile-ssh and run the script. Yes, guix can do that. But the
guix daemons weren’t running.
next reply other threads:[~2016-02-22 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:08 Arne Babenhauserheide [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 15:08 What is needed in guildhall to include it in Guile? Arne Babenhauserheide
2016-02-22 17:57 ` Nala Ginrut
2016-02-23 16:57 ` Arne Babenhauserheide
2016-02-23 22:50 ` Arne Babenhauserheide
2016-03-23 19:32 ` Arne Babenhauserheide
2016-03-23 22:54 ` Christopher Allan Webber
2017-03-01 19:35 ` Amirouche
2017-03-01 20:34 ` Amirouche
2017-03-03 23:05 ` Amirouche
2016-02-22 18:17 ` Christopher Allan Webber
2016-02-22 19:18 ` Jan Nieuwenhuizen
2016-02-22 20:26 ` Panicz Maciej Godek
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=87h9h01yr4.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@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).