From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile & Emacs chat at emacs hackathon/bug-crush SF
Date: Wed, 16 Mar 2016 12:55:15 +0100 [thread overview]
Message-ID: <CAA2Xvw+mbOvJ1kEh3-6Mkf9Lktv6Ts9ztCL1PkxrvTWLkRXnLA@mail.gmail.com> (raw)
In-Reply-To: <87egbo0zxc.fsf@dustycloud.org>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
This is wonderful news! :-)
I've actually tried out guile-emacs recently. What would be wonderful to
have is some kind of simple "map" over what has been done so far (e.g. the
large-scale structure of the code and what the relationship between the
elisp and guile interpreter currently is). Maybe that exists and I didn't
find it?
Best regards,
Mikael D.
On Sun, Mar 6, 2016 at 9:32 AM, Christopher Allan Webber <
cwebber@dustycloud.org> wrote:
> Heya everyone,
>
> I was at the Emacs hackathon / bug crushing event and I gave a couple
> demos that were Guile related, one showing off guile-emacs, and one
> showing off Guix's Emacs integration. So the good news is: the talk
> went super, super well (on both, but especially guile-emacs), and
> enthusiasm was high! When I showed guile-emacs live, there were some
> amazed expressions to see oh hey... this is *really* working!
>
> I also had a conversation with John Wiegley, current maintainer of
> emacs, and he said several things:
>
> - He thinks it would be *great* to have Emacs running on Scheme, a
> clear win, assuming it's integrated and runs fast and works well.
>
> - However, Guile would have to be able to make a promise: once Emacs
> ran on top of Guile, Emacs would have to be able to have say over
> anything that could end up changing actual semantics in Emacs
> (mainly, anything that would break Emacs user's source code).
>
> (I think there's an easy answer to this: guile-emacs is already
> aiming for heavy backwards compatibility and should just preserve
> that at this level.)
>
> - If we could prove that performance was better in guile-emacs, that's
> an easy way to win enthusiasm.
>
> - A good goal to work towards: all of emacs' tests should pass using
> guile-emacs.
>
> So that's all a ways off, but I'm feeling enthusiastic that it's
> possible!
>
> - Chris
>
> PS: I'd like to see bipt's elisp branch merged with master. I might try
> to help... I'm trying to learn enough to do so. However I don't have a
> lot of time, and especially not a lot of experience with compilers..
>
>
[-- Attachment #2: Type: text/html, Size: 2684 bytes --]
next prev parent reply other threads:[~2016-03-16 11:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 8:32 Guile & Emacs chat at emacs hackathon/bug-crush SF Christopher Allan Webber
2016-03-06 16:53 ` Christopher Allan Webber
2016-03-07 1:01 ` What's needed to get elisp updates into Guile master? Christopher Allan Webber
2016-03-07 10:14 ` Mathieu Lirzin
2016-03-07 18:06 ` Christopher Allan Webber
2016-03-07 19:12 ` Mathieu Lirzin
2016-03-08 1:23 ` Christopher Allan Webber
2016-03-09 9:07 ` Taylan Ulrich Bayırlı/Kammer
2016-03-09 17:22 ` Christopher Allan Webber
2016-03-11 1:51 ` Elisp branch ready for merge (??) Christopher Allan Webber
2016-03-11 9:44 ` Taylan Ulrich Bayırlı/Kammer
2016-03-11 16:33 ` Christopher Allan Webber
2016-03-12 12:40 ` Taylan Ulrich Bayırlı/Kammer
2016-03-12 17:15 ` Christopher Allan Webber
2016-03-11 13:14 ` Mathieu Lirzin
2016-03-11 16:30 ` Christopher Allan Webber
2016-03-11 17:56 ` Mathieu Lirzin
2016-03-25 19:06 ` Christopher Allan Webber
2016-03-16 11:55 ` Mikael Djurfeldt [this message]
2016-03-16 18:58 ` Guile & Emacs chat at emacs hackathon/bug-crush SF Stefan Husmann
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=CAA2Xvw+mbOvJ1kEh3-6Mkf9Lktv6Ts9ztCL1PkxrvTWLkRXnLA@mail.gmail.com \
--to=mikael@djurfeldt.com \
--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).