News for hackers. Stuff that matters.

A comment on Clarifying some things about Guile-Emacs. Parent comment

Re:Clarifying some things about Guile-Emacs by mapcar on Friday September 19, 2014 @07:35AM (#8339930)
Right, it's the "pretty much" part that's a little disturbing. Would be nice to know why this caveat is always thrown around.
[ Parent | on HN ]
Re:Clarifying some things about Guile-Emacs by rcthompson on Friday September 19, 2014 @03:41PM (#8342109)
Well, the message gives specific examples of the kinds of code that might need to be modified: "debuggers, macroexpanders and code-walkers".
[ Parent | on HN ]
Re:Clarifying some things about Guile-Emacs by tedks on Friday September 19, 2014 @03:19PM (#8342022)
I think this is incorrect, the point of Guile-Emacs is to implement support for all Emacs Lisp in Guile. No backwards-incompatibility will be present in whatever Emacs eventually moves to.
[ Parent | on HN ]
Re:Clarifying some things about Guile-Emacs by davexunit on Friday September 19, 2014 @09:08AM (#8340294)
One example is that some extensions such as Gnus have contain code written in the current Elisp interpreter's bytecode, which is incompatible with the Guile VM.
[ Parent | on HN ]
Re:Clarifying some things about Guile-Emacs by parfe on Friday September 19, 2014 @10:54AM (#8340773)
From the submitted email:

>Guile-Emacs loads, compiles and executes the programs included in Emacs by default, plus Gnus, Org-Mode, and more.

[ Parent | on HN ]