From: "Gerry Agbobada" <guile@gagbo.net>
To: rekado@elephly.net
Cc: guile-devel@gnu.org
Subject: Re: rebased wip-elisp
Date: Sun, 28 Mar 2021 21:00:56 +0200 [thread overview]
Message-ID: <74f626de-67a2-4834-8bbd-67c3749a1711@www.fastmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Hello,
Thanks for the rebase on top of guile 2.2, I'd like to see how I could learn enough to contribute to elisp support in guile. I really don't have a lot of experience looking at guile code so sorry for the seemingly bad questions :
- you say that the tests pass for you, but I had an issue with one test-out-of-memory, I could not trigger the out-of-memory error on the `make-bytevector` call. Did you have the same issue as well or is it something that only stems from my computer ?
- Is there a common manifest.scm/ <http://manifest.scm/profile>guix profile to use when hacking on guile ?
- Is there a make target for the guile-emacs that you had and segfaulted ?
Thanks in advance for the answers,
Gerry Agbobada
[-- Attachment #2: Type: text/html, Size: 981 bytes --]
next reply other threads:[~2021-03-28 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 19:00 Gerry Agbobada [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-16 21:52 rebased wip-elisp Ricardo Wurmus
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=74f626de-67a2-4834-8bbd-67c3749a1711@www.fastmail.com \
--to=guile@gagbo.net \
--cc=guile-devel@gnu.org \
--cc=rekado@elephly.net \
/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).