blocks|key|1762544|text|guile和emacs，再次更新Emacs+src，使用非黑客Guile，2009年8月23日|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1762545|1762546|+PS:我最近注意到，我第一次提交与该项目相关的Emacs源码树是在1999-08-28，不到十年前。我不确定我是应该在周五庆祝还是沮丧。|blockquote|1762547|1762548|1762549|http://lists.gnu.org/archive/html/guile-devel/2009-08/msg00163.html|1762550|entityMap|0|LINK|mutability|MUTABLE|url^0|0|10|0|0|0|0|0|0|1V|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|Y|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|N|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|M]]]]

guile and emacs, again - updated Emacs src, using non-hacked Guile, 23 Aug 2009

<blockquote>
 PS: I was noticing recently that my first
 commit to the Emacs source tree
 relating to this project was on
 1999-08-28, just shy of ten years ago.
 I'm not sure if I should celebrate or
 be depressed on Friday.
</blockquote>

<a href="http://lists.gnu.org/archive/html/guile-devel/2009-08/msg00163.html" rel="noreferrer">http://lists.gnu.org/archive/html/guile-devel/2009-08/msg00163.html</a>

blocks|key|1764567|text|在Guile2.0发布之后，在Emacs中使用Guile应该是可能的。当前的预发布支持ecmascript以及scheme，显然还有一个elisp分支，但我还没有研究过它。一旦Guile完全支持elisp，用Guile替换当前的elisp解释器应该不会太难。真正的问题是，人们是否会在scheme中重写他们的自定义和附加组件，或者只是继续使用elisp。无论如何，Guile2.0应该会使Guile+Emacs的可能性比过去10年中的任何其他开发都更接近现实。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1764568|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It should be possible after Guile 2.0 is released to use Guile with Emacs. The current pre-release supports ecmascript as well as scheme and there is apparently an elisp branch also but I haven't looked into it. Once Guile fully supports elisp it shouldn't be too hard to replace the current elisp interpreter with Guile. The real question is whether or not people are going to rewrite their customizations and add-ons in scheme or just continue to use elisp. Regardless, Guile 2.0 should make the possibility of a Guile Emacs much closer to reality than any other development in the past 10 years.

blocks|key|1801144|text|Guile+2.0.0+(发布于2011-02-06)支持Emacs+Lisp。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1801145|你可以像这样在repl上切换：|1801146|+scheme@(guile-user)>+,language+elisp
+Happy+hacking+with+Emacs+Lisp!++To+switch+back,+type+`,L+scheme'.
+elisp@(guile-user)>+(eq+1+2)
+$1+=+#nil|code-block|syntax|javascript|1801147|至于是否/什么时候有人要在Emacs上做一些手术来提取elisp并以Guile-+in+-elisp模式下降：Guile+2.0.2+reference+manual建议这是计划，但还没有准备好：|offset|length|1801148|1801149|我们希望最终Guile对Elisp的实现将足够好，以取代Emacs自己的Elisp实现。|blockquote|1801150|1801151|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/guile/manual/guile.html#Emacs-Lisp^0|0|0|0|1J|S|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|12|8|@]|9|@$K|13|L|14|1|15]]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|17|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

Guile 2.0.0 (released 2011-02-06) supports Emacs Lisp.

You can switch at the repl like so:

<pre><code> scheme@(guile-user)&gt; ,language elisp
 Happy hacking with Emacs Lisp! To switch back, type `,L scheme'.
 elisp@(guile-user)&gt; (eq 1 2)
 $1 = #nil
</code></pre>

As to if/when someone is going to do some surgery on Emacs to extract elisp and drop in Guile-in-elisp-mode: the <a href="http://www.gnu.org/software/guile/manual/guile.html#Emacs-Lisp">Guile 2.0.2 reference manual</a> suggests this is the plan but it's not ready yet:

<blockquote>
 We hope that eventually Guile's
 implementation of Elisp will be good
 enough to replace Emacs' own
 implementation of Elisp.
</blockquote>

blocks|key|1762595|text|最近关于这个话题有一些有趣的讨论：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1762596|1762597|http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00665.html|unordered-list-item|offset|length|1762598|http://wingolog.org/archives/2010/04/02/recent-developments-in-guile|1762599|1762600|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|1V|0|0|0|1W|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@$F|V|G|W|1|X]]|A|$]]|$1|H|3|I|5|E|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|D]]|R|$5|N|O|P|A|$Q|I]]]]

There have been some interesting discussions on this topic in recent times:

<ul>
<li><a href="http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00665.html" rel="nofollow noreferrer">http://lists.gnu.org/archive/html/emacs-devel/2010-04/msg00665.html</a></li>
<li><a href="http://wingolog.org/archives/2010/04/02/recent-developments-in-guile" rel="nofollow noreferrer">http://wingolog.org/archives/2010/04/02/recent-developments-in-guile</a></li>
</ul>

blocks|key|463973|text|我不会太担心这件事。有几个项目可以在Emacs中使用Guile，但我感觉它们并不受主流支持。正如其中一个项目的开发人员所观察到的那样，除非他们现有的所有elisp都能在新引擎中完美运行，否则没有人会切换，这是一项相当艰巨的任务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|463974|这并不是说它永远不会发生，只是它已经“在云中”有几年了。|463975|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I wouldn't worry too much about it. There are a couple of projects to use Guile with Emacs, but I sense that they're not mainline supported. As one of the developers of one of the projects observed, no one will switch unless all their existing elisp runs flawlessly in the new engine, which is a pretty tall task.

Not that it will never happen, it's just been 'in the clouds' for a few years.

blocks|key|464029|text|在未来，使用像parrot这样的VM似乎比Guile更有趣，因为Parrot可以处理many+different+dynamic+languages，并且每种语言都可以重用用另一种语言开发的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|464030|剩下的工作是：|464031|464032|将emacs低级概念和函数添加到Parrot+VM+(基本elisp类型，如缓冲区类型、窗口、frame...)|unordered-list-item|464033|creating+a+elisp语言端口到Parrot+VM。|464034|464035|有了这样的功能，您可以让所有遗留的elisp代码在Parrot上运行，而不会出现任何移植问题，并且可以通过Parrot支持的任何语言开发和重用新代码。|464036|entityMap|0|LINK|mutability|MUTABLE|url|http://www.parrot.org/|1|http://www.parrot.org/languages^0|7|6|0|16|W|1|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|16|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|17|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|18|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|19|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1A|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]|W|$5|R|S|T|C|$U|X]]]]

Using a VM like <a href="http://www.parrot.org/" rel="nofollow noreferrer">parrot</a> seems more interesting for the future than Guile as Parrot VM can handle <a href="http://www.parrot.org/languages" rel="nofollow noreferrer">many different dynamic languages</a> and each language can reuse what has been developed in another language.

The work left to be done is :

<ul>
<li>adding emacs low-level concepts and functions to Parrot VM (basic elisp types like the buffer type, window, frame...)</li>
<li>creating an elisp language port to Parrot VM.</li>
</ul>

With such functionalities you could have all legacy elisp code running on Parrot VM without any porting issues, and new code could be developed and reused by any language supported by Parrot VM.

I'm learning Emacs Lisp and I came across this decade old post saying that at some point Guile (Scheme) will replace Emacs Lisp, or Emacs will be rewritten with Guile. 

<a href="https://web.archive.org/web/20081201143448/http://sanpietro.red-bean.com/guile/guile/old/3114.html" rel="nofollow noreferrer">https://web.archive.org/web/20081201143448/http://sanpietro.red-bean.com/guile/guile/old/3114.html</a>

I was wondering if this is still a possibility, and if developers should be trying to write Elisp with this in mind? The original goal was for Guile to be backwards compatible with Elisp, but it seems like developing Scheme is the better choice.

Guile and Emacs?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在学习Emacs Lisp，我偶然看到这篇十年前的帖子说Guile (Scheme)将在某一时刻取代Emacs Lisp，或者Emacs将被Guile重写。我想知道这是否仍然有可能，开发人员是否应该在编写Elisp时考虑到这一点？最初的目标是让Guile向后兼容Elisp，但似乎开发Scheme是更好的选择。

问Guile和Emacs？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Guile和Emacs？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Guile和Emacs？
EN