3 ms·
It's bound to emacs because it is written in emacs-lisp. It's a large, sophisticated codebase that dates back almost 20 years. There is no way it could ever be
by da39a3ee 6y ago
It's bound to emacs because it is written in emacs-lisp. It's a large, sophisticated codebase that dates back almost 20 years. There is no way it could ever be ported to another language in its entirety: it is very tightly bound into the (also sophisticated) string manipulation APIs available in emacs lisp.
- tgbugs 6y agoTechnically it could be ported, but that port would require porting a major subset, if not all of emacs lisp as well. This is due to the fact that elisp closures are valid and often semantically critical arguments to src blocks. Defining the features that must be implemented to achieve a certain level of org-mode support and compatibility is something that definitely needs to be tackled in the future.