News for hackers. Stuff that matters.
Re:Removing support for Emacs unexec from Glibc by Decade on Saturday January 30, 2016 @01:30PM (#11003065)
The host platform has no reason to exist except to run programs. And then functionality that turns out to be widely useful goes into the standards.

So, it turns out that unexec has not made it into the standards, and now is causing more problems than it’s solving, and the glibc maintainers are going to remove it.

This would not be an interesting story, except that it involves Emacs, Stallman, and the appropriate use of mailing lists. Still, the conclusion of the article is that the process works and everything’s just going fine.

Re:Removing support for Emacs unexec from Glibc by xxpor on Saturday January 30, 2016 @03:12PM (#11003526)
It may not be an interesting story from that perspective, but from the perspective of an emacs user, I had no idea that emacs did this. Reading about how it works has been super interesting (with a healthy dose of wat thrown in). I'm glad it was posted.
Re:Removing support for Emacs unexec from Glibc by TheCondor on Saturday January 30, 2016 @03:51PM (#11003676)
It's worth compiling emacs and understanding it all. It is interesting.
Re:Removing support for Emacs unexec from Glibc by semi-extrinsic on Saturday January 30, 2016 @06:00PM (#11004200)
So let me see if I get this. The build process runs a huge autoconf etc., then compiles from C code a proto-emacs, which is then executed and loads up a bunch of Lisp code, then a (self-described as) ugly hack is used to dump that running program (including the loaded Lispy-bits) as a new executable, which is your editor? Wow.