From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Mike Gran <spk121@yahoo.com>
Subject: Re: Editing Scheme in the installation image
Date: Sat, 07 Jan 2017 14:44:58 -0800 [thread overview]
Message-ID: <87y3ym1od1.fsf@gmail.com> (raw)
In-Reply-To: <87pojzf5l9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 07 Jan 2017 12:54:26 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mike Gran <spk121@yahoo.com> skribis:
>
>> The functions expressed in Scheme in Zile-on-Guile are the same
>> as upstream Zile had. It is a fairly limited set.
>> Zile-on-Guile is a Scheme, not an elisp, even though the functions
>> it expresses have elisp-like names. So there is little portability
>> between Emacs and this Zile.
>
> Yes. Any idea how hard it would be to port the real Paredit to
> Zile-on-Guile?
Isn't there native support for elisp in Guile? Would this allow running
directly Paredit (elisp), provided that Zile-on-Guile implements
everything that Paredit needs from the Emacs API?
This is probably more work in the short term than rewriting Paredit in
Scheme, but it would enable Zile-on-Guile to potentially run (m)any Emacs
packages.
Maxim
next prev parent reply other threads:[~2017-01-07 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 23:05 Editing Scheme in the installation image Ludovic Courtès
2017-01-06 1:54 ` Kei Kebreau
2017-01-06 9:09 ` Ricardo Wurmus
2017-01-06 13:49 ` Mike Gran
2017-01-07 11:54 ` Ludovic Courtès
2017-01-07 22:44 ` Maxim Cournoyer [this message]
2017-01-08 10:48 ` Ludovic Courtès
2017-01-08 18:43 ` Mike Gran
2017-01-08 22:43 ` Ludovic Courtès
2017-01-09 1:27 ` Christopher Allan Webber
2017-01-09 9:10 ` Ludovic Courtès
2017-01-07 16:00 ` Christopher Allan Webber
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3ym1od1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=spk121@yahoo.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.