From: "Gregg Sangster" <gregg@thesangsters.ca>
To: "Christine Lemmer-Webber" <cwebber@dustycloud.org>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, guile-devel@gnu.org
Subject: Re: Guile 3 and wip-elisp/Emacs
Date: Thu, 14 Oct 2021 16:01:33 +0200 [thread overview]
Message-ID: <47-61683800-21-6332ae00@62794253> (raw)
In-Reply-To: <871r5ti5k4.fsf@dustycloud.org>
Hello,
I have wip-elisp rebased all the way up to main as of a few days ago (e60469c8b6936575c079faaffa40a340e1d49f3c) plus two changes from Ricardo. It's available here:
https://git.sr.ht/~g20r/guile
There is one test failure in "make check" on test-out-of-memory. I haven't investigated it yet but I get the same failure on main. If that's not an expected failure, it might be a problem with my environment.
There is also an emacs repo here:
https://git.sr.ht/~g20r/emacs
which uses the 3.0-based wip-elisp. It builds and runs but segfaults easily. I've started rebasing it on a more current emacs. Those changes aren't published yet.
I haven't been able to get the guile-emacs package in guix working. The build gets stuck at collecting/processing OKURI-NASI entries after a few hours. For comparison, the 3.0-based guile-emacs builds in about 20 minutes on my machine. If anyone has that running, it would be nice to have a comparison of the build/run speed.
On Sunday, September 12, 2021 22:13 EDT, Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>
> > [[PGP Signed Part:Undecided]]
> > Hello Gregg,
> > "Gregg Sangster" <gregg@thesangsters.ca> writes:
> >
> >> I've rebased the wip-elisp branch on top of commit
> >> 449f50dd84a081aea16ef678e32bf37abe429ff6 (git describe:
> >> v3.0.4-64-g33232cb5c4). It's published here:
> >>
> >> https://git.sr.ht/~g20r/guile
> >
> > I’m not a Guile core developer, but I think that this is awesome!
> >
> >> My question is if this is worthwhile work? I don't have much time to
> >> spend on it but am happy to keep hacking away if there's still
> >> upstream interest.
> >
> > I think that there is upstream interest in Guile to improve the elisp
> > implementation, but I’m not sure about Emacs. They added improvements to
> > elisp that also provide better performance and they keep improving their
> > elisp implementation.
>
> I would personally think it would be good if we could get the wip-elisp
> branch merged. It would be good not to bitrot. It seems more likely to
> survive if it gets included in emacs proper.
>
> > That said: Tools like fibers would be great to have in Emacs.
> >
> > The workload to finish this is considerable, though: IIRC You’ll need to
> > solve some deeper problems that prevent Guile Emacs from using
> > byte-compiled files (that’s why it currently has a very high startup
> > time).
> >
> > That said, there is a guile-emacs package in guix, and Guile 3.0.7 is
> > much faster than Guile 2.
>
> Yes, to complete *guile-emacs*... that will be a lot of work. But it
> will be less work if guile's elisp branch is no longer this separate
> thing that isn't kept up to date with the rest of guile. More likely
> that someone could finish and pick it up.
>
> > (please someone correct me if I’m wrong!)
> >
> > Best wishes,
> > Arne
>
next prev parent reply other threads:[~2021-10-14 14:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 15:12 Guile 3 and wip-elisp/Emacs Gregg Sangster
2021-09-10 19:59 ` Dr. Arne Babenhauserheide
2021-09-13 2:13 ` Christine Lemmer-Webber
2021-10-14 14:01 ` Gregg Sangster [this message]
2021-10-14 17:34 ` Ricardo Wurmus
2021-10-20 10:56 ` Gregg Sangster
2021-10-21 14:05 ` Ricardo Wurmus
2021-10-21 17:49 ` Robin Templeton
2021-10-20 11:59 ` Robin Templeton
2021-09-13 10:56 ` Ricardo Wurmus
2021-09-20 10:39 ` Gerry Agbobada
2021-10-14 13:35 ` Gregg Sangster
2021-10-16 5:25 ` Christine Lemmer-Webber
2021-10-19 21:59 ` Christine Lemmer-Webber
2021-10-19 22:29 ` Ludovic Courtès
2021-10-20 1:46 ` Christine Lemmer-Webber
2021-10-20 2:51 ` Christine Lemmer-Webber
2021-10-20 16:27 ` Christopher Allan Webber
2021-10-22 16:11 ` Christine Lemmer-Webber
2021-10-22 16:17 ` Christine Lemmer-Webber
2021-10-22 18:38 ` Gregg Sangster
2021-10-21 19:34 ` Robin Templeton
2021-10-22 2:59 ` Christine Lemmer-Webber
2021-10-20 10:43 ` Gregg Sangster
2021-10-20 11:43 ` Robin Templeton
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 15:09 Gregg Sangster
2021-09-10 15:09 Gregg Sangster
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=47-61683800-21-6332ae00@62794253 \
--to=gregg@thesangsters.ca \
--cc=arne_bab@web.de \
--cc=cwebber@dustycloud.org \
--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).