[atilaneves]

> What do you think, is there a potential niche for like NeoEmacs, a test editor written in a modern Lisp / Scheme

I think that's a non-starter because you instantly lose the entire ecosystem of elisp packages out there and nobody's config would work anymore. The latter is especially important when for some people that's a decades-developed init.el file in a repo that's migrated from CVS to subversion then git.

I've git bisected (mercurial at the time, but whatever) my .emacs repo to figure out what I did to break my Python config, so there's that.

[DerArzt]

You may have a misunderstanding here. Neovim, while it is a ground up rewrite of vim, didn't break people's configs. The team made it a point to maintain backwards compatibility while positioning themselves to be able to move towards using lua as their config language.

[pritambaral]

Yes, but then Vimscript wasn't a very good language; whereas Lua, Python (and many others Neovim enabled support for) are great languages.

The benefit of a much better language is enticing; making a language much better than Emacs Lisp, however, is not so easy.

[blacktriangle]

Except the specific rewrite the op was talking about was moving from elisp to scheme. It's one thing to support a limited language like vimscript, it's a whole other thing to reproduce the semantics of elisp in scheme.