Remacs – A community-driven port of Emacs to Rust

Re:Remacs – A community-driven port of Emacs to Rust by melling on Sunday July 16, 2017 @12:29PM (#14782700)

A large part of Emacs is the Lisp source. It would be great to have another interpreter written in Rust that reads the same Lisp files.

What’s the breakout of C vs Elisp?

Ideally more of Emacs could be rewritten in Lisp with a smaller interpreter.

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by mschaef on Sunday July 16, 2017 @12:45PM (#14782798)

The last numbers I heard were from a few years ago, but on the order of 250KLOC of C and 1MLOC of Emacs Lisp. There's a lot there (and some of it gets fairly exotic around redisplay, unexec, etc.)

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by sillysaurus3 on Sunday July 16, 2017 @02:31PM (#14783426)

349,615 lines of C

1,632,280 lines of elisp

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by znpy on Sunday July 16, 2017 @02:45PM (#14783508)

Also... I have dug the emacs sources for a while and i can testify that many times, function have two, three (sometimes more) actual implementations that gets actually built depending on configuration (example: sunos va dos vs linux vs win32 version of function foo).

So... Yeah. The c lines are in a way, "overcounted".

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by Ar-Curunir on Sunday July 16, 2017 @05:40PM (#14784245)

No... those lines still have to be maintained and kept in sync, otherwise you end up with bugs. So it's not over counting, because there is still work associated with these different implementations

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by flavio81 on Sunday July 16, 2017 @08:20PM (#14784812)

>It would be great to have another interpreter written in Rust that reads the same Lisp files.

Agree, but then we would have a new case of Greenspun's 10th rule.

[ Parent | on HN ]