3 ms·

Also, from a back-of-the-envelope calculation from the ohloh.net numbers, Emacs has ~1.1M LoC of ELisp. With that kind of number, you're pretty much guaranteed

• ThatGeoGuy 10y ago
  This is probably the main misconception: Guile is only included to change the underlying Elisp implementation, not to completely change everything from Elisp to Scheme. The problem is mostly getting maintainers to switch over (as most are old enough to have dabbled in the current Elisp engine at least a few times, if not helped write the original implementation). So yeah, it's not so much the Elisp in the Emacs source that's the problem, it's how do the maintainers switch to maintaining Elisp inside of the Guile project (up until now, Elisp was maintained as a language alongside Emacs). At the very least, this is how I understand it.
  • rhabarba 10y ago
    There are large packages like Gnus and TRAMP which are directly developed inside (and distributed with) Emacs, but, in theory, they should "just work" in the Guile version even after XEmacs support was dropped, right?
• fafner 10y ago
  And that does not include any external packets... Yes, there is no way Emacs will get rid of elisp. That's why Guile Emacs includes writing an elisp frontend for Guile. (There is also a Frontend for ECMAScript and an experimental one for Lua)