News for hackers. Stuff that matters.
Re:The Emacs dumper dispute by sooheon on Wednesday November 30, 2016 @02:45PM (#13073984)
God a neomacs written in a faster, more modern lisp would be a dream.
Re:The Emacs dumper dispute by bryanlarsen on Wednesday November 30, 2016 @02:53PM (#13074087)
Re:The Emacs dumper dispute by AceJohnny2 on Wednesday November 30, 2016 @03:31PM (#13074427)
Guile Emacs isn't a bottom-up rewrite of Emacs [1], but a project to replace the elisp runtime with Guile. One important thing it does not do is get rid of/convert any ELisp, because of how much is invested in it: 71% of the ~2M LOC codebase is ELisp: https://www.openhub.net/p/emacs

Guile would run the ELisp code. What's holding the project back, IIRC, is that it doesn't yet do so perfectly.

[1] which is something I (and likely most users) frequently think it sorely needs, until we realize A) the monumental size of the task and B) how much refinement the current version already has, as per http://www.joelonsoftware.com/articles/fog0000000069.html

Re:The Emacs dumper dispute by fatbird on Wednesday November 30, 2016 @03:01PM (#13074183)
Interesting. Any idea on why it's not got more traction? Or is it actually on track to become the canonical emacs?

Reading that LWN article, it looks like Guile wasn't a great choice from a community perspective, but more than that, by working internally to the emacs project it's subjected itself to internal standards of interoperability that it'll never really be able to hit (where a pseudo-hostile fork like xEmacs was might have sufficient momentum to force some accommodation).

Re:The Emacs dumper dispute by sedachv on Wednesday November 30, 2016 @07:59PM (#13076128)
> Reading that LWN article, it looks like Guile wasn't a great choice from a community perspective

I think going forward it will be. Between Guile-Emacs, Guix, and GNU Shepherd you have the best-supported Lisp Machine operating system analogue available right now: https://www.gnu.org/software/guix/

I am excited about GuixSD and I think a lot of other people will be.

Re:The Emacs dumper dispute by armitron on Wednesday November 30, 2016 @09:40PM (#13076742)
No it wont, at least as far as Emacs is concerned.

Nobody is stepping up to do the work, plus Guile has serious bugs on Windows and OSX, single-digit number of developers and few, if any, users. So Guile Emacs is really a pipe dream that people like to bring up from time to time.

Re:The Emacs dumper dispute by sedachv on Thursday December 01, 2016 @05:16AM (#13078445)
> Nobody is stepping up to do the work, plus Guile has serious bugs on Windows and OSX, single-digit number of developers and few, if any, users. So Guile Emacs is really a pipe dream that people like to bring up from time to time.

You forgot to mention that BSD is dying.

This state of affairs is different from any other Lisp implementation how? And why would it stop progress from being made?

Re:The Emacs dumper dispute by armitron on Saturday December 03, 2016 @04:59PM (#13097712)
I've been happily running SBCL and CCL on Linux and OSX for years without issues. CCL on Windows too.

Guile has 1-2 people working on it part-time, and Windows/OSX are not a priority because:

+ GNU project, duh.

+ Nobody in Guile-land cares about Windows/OSX enough to step up and fix issues.

+ Even if they did, Stallman would tell them not to.

So the state of affairs is indeed very different from the CL Lisp implementations. Not to mention, Guile has pretty much no userbase to speak of. There are commercial entities releasing products with SBCL and CCL in addition to the very healthy opensource community.

Re:The Emacs dumper dispute by lispm on Friday December 02, 2016 @02:22AM (#13086788)
> best-supported Lisp Machine operating system analogue

Hardly. GNU is far from anything Lisp Machine. The Lisp Machine was never a system hacked up by scripts running on top of some Unix copy with a fancy name.

Re:The Emacs dumper dispute by qwertyuiop924 on Wednesday November 30, 2016 @03:32PM (#13074433)
It sorta works, but it's hard to keep it working, so people don't really do much with it.

Shockingly, the compatability was pretty good, last I checked.

If you really want an emacs written in a sane Lisp, and don't mind losing gnuemacs compatability, check out Hemlock. or Edwin.

Re:The Emacs dumper dispute by draven on Wednesday November 30, 2016 @03:54PM (#13074599)
> check out Hemlock. or Edwin.

Or Climacs https://www.common-lisp.net/project/climacs/

It seems there's a rewrite as well: https://github.com/robert-strandh/Second-Climacs

Re:The Emacs dumper dispute by qwertyuiop924 on Wednesday November 30, 2016 @04:39PM (#13074945)
Oh. I forgot Climacs.

Well, there you go. Another CL editor.

Re:The Emacs dumper dispute by lispm on Thursday December 01, 2016 @01:19AM (#13077580)
Here is another one:

https://github.com/cxxxr/lem

Re:The Emacs dumper dispute by zeveb on Wednesday November 30, 2016 @03:34PM (#13074449)
As I note elsethread, Guile Scheme is not a 'faster, more modern Lisp,' because Scheme is not Lisp. Scheme is a Lisp-like language, which does have a place in the world, but it's not Lisp, and it's not (IMHO) well-suited for large software projects like emacs.

I personally oppose a Scheme-based emacs because, having moved from C to a more Lisp-like language, I don't think there would be the will to actually move to real Lisp. You might accuse me of letting the best be the enemy of the good (which is a fair criticism, both of my position re. porting emacs & of Zaretskii's re. the dumper), but part of why I use emacs and Lisp is that they are not good: they are the best.

Re:The Emacs dumper dispute by loup-vaillant on Thursday December 01, 2016 @07:32AM (#13078922)
Emacs-Lisp is dynamically scoped. That's precisely the kind of mistake (yes, mistake), that hinders large scale anything.

And who cares Scheme is not Lisp? It's close, and it's reputedly cleaner. Besides, there are many Lisp dialects, some of them just as different from one another than Scheme is from them.

Re:The Emacs dumper dispute by zeveb on Thursday December 01, 2016 @10:54AM (#13080208)
> Emacs-Lisp is dynamically scoped. That's precisely the kind of mistake (yes, mistake), that hinders large scale anything.

Yup, default-dynamic scope is a mistake, although in the particular case of emacs it has made certain code very clean (and led to plenty of bugs, as well). Emacs has added lexical scoping, which is a start.

Common Lisp's lexical default and optional dynamic scoping provides the best of both worlds.

> And who cares Scheme is not Lisp? It's close, and it's reputedly cleaner.

Among other things, its continuations are semantically broken, preventing correct implementation of UNWIND-PROTECT.

It's a good language for its intended purpose (teaching & research), but the language as standarised is not well-suited for building large projects (individual implementations, of course, can be quite good — but then one enters the world of implementation-dependence).

Common Lisp is superior for large projects, in part because it's much more fully-specified, in part because that specification includes more features, in part culturally (because Lisp systems have more often tended to be large and long-lasting).

Re:The Emacs dumper dispute by kazinator on Thursday December 01, 2016 @06:02PM (#13084424)
In TXR Lisp, a Common-Lisp-like language which has (delimited) continuations, I came up with a pragmatic approach w.r.t. unwind-protect which works well.

I introduced "absconding" operators which allow a context to be abandoned (via a non-local exit) without invoking unwinding. Absconding just performs the jump to the exit point, without doing any clean up along the way. That's it!

The idea is basically: why, when temporarily leaving a continuation, should we clean up resources, when we intend to resume the continuation and want those resources intact? If it should happen that we don't resume, so what; garbage collection will just have to take care of it. We wouldn't do that with threads, or coroutines, right? When a thread suspends, we don't close its files for fear that it might never wake up to use them and close them.

With this absconding, I implemented a workable yield construct. I can have code which, say, recursively traverses some structure and yields items to a controlling routine. That recursion can have exception handling and unwinding which works normally, as if the yields were not there. When the recursion performs a normal return, or a throw, all the unwinding takes place normally. The yields use absconding, and so they don't disturb anything. When a continuation is resumed, all of the dynamic handlers are in place, including the unwind cleanups that were never touched. Nothing was torn down.

Also in place are dynamically scoped variables. TXR Lisp's continuations play nicely with those also.

If you compare this brilliantly simple solution to concoctions involving dynamic-wind, dynamic-wind looks hopelessly silly, like what were they thinking when they came up with it?

Just don't unwind when you temporarily leave a context. The sky does not fall. Your CS degree is still hanging the wall. Everything is cool.