unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Robin Templeton <robin@terpri.org>
To: guile-devel@gnu.org
Subject: Re: Guile 3 and wip-elisp/Emacs
Date: Wed, 20 Oct 2021 07:59:17 -0400	[thread overview]
Message-ID: <87a6j3nbze.fsf@terpri.org> (raw)
In-Reply-To: 87zgskrybd.fsf@web.de

"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:

> 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).

To clarify, Guile-Emacs intentionally ditches the existing Emacs
bytecode compiler entirely (though it'd probably be possible to emulate
the bytecode interpreter to allow loading old '.elc' files). I haven't
followed Guile development closely enough to know whether these are
practical solutions, but my main ideas for improving startup speed were
to either add some form of AOT compilation to Guile, or to rely on
cached JIT-compiled code. IIRC Emacs now uses a portable dumper (rather
than the old system which dumped a running Emacs instance to an
executable), which seems analogous to the latter approach.

> That said, there is a guile-emacs package in guix, and Guile 3.0.7 is
> much faster than Guile 2.
>
> (please someone correct me if I’m wrong!)
>
> Best wishes,
> Arne

Regards,
Robin

-- 
<Robert> But speaking of programming, I was dreaming that I had some
coding problem and suddenly robin walked by, so I asked what the common
lisp way of solving it would be.




  parent reply	other threads:[~2021-10-20 11:59 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
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 [this message]
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=87a6j3nbze.fsf@terpri.org \
    --to=robin@terpri.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).