On Jan 02 2008 19:34 +0330, >> As a thought experiment, I would like to ask, suppose we waved a magic >> wand and produced a complete (whatever that means) Python (swig?) >> wrapper for Emacs: the *real* Emacs. > > One part of this idea would be to create an Emacs module in the > standard python library. Something like: > > import emacs > editor = emacs.editor() > editor.run() > > All details hazy. Presumably, there would be ways to augment or > override the emacs startup code. And we would probably want the > following: > > editor.executeElispFunction(name-of-elisp-function) > > and > > editor.executePythonScript(aPythonScript) > > BTW, pymacs allows something like this. It's not clear to me whether > anything 'better' than pymacs is even conceivable.
Pymacs is really a nice tool. But it has not been maintained in the last few years. Since ropemacs (rope plugin for emacs) depends on it and I needed to fix some of its problems I've started a mercurial repo to make my fixes on it: * repo: http://rope.sf.net/hg/rpymacs * snapshot: http://rope.sf.net/hg/rpymacs/tip.tar.gz I'll be happy if someone maintains pymacs once more (if no one volunteers, I'll be happy to). Regards, -- Ali
