> I am not sure [pida] is exactly what you mean, but it is certainly a > viable approach to achieving some of the things you are hinting about.
Very interesting. I just glanced at the pida handbook and found this: "PIDA is different from other IDEs in that it will use the tools that are already available rather than attempting to reinvent each one." It was exactly this kind of thought lead me to the thought experiment of wrapping Emacs. Here is another quote from the pida handbook: "PIDA is essentially a bunch of services bound together by a Boss. The services are discovered from service directories and loaded by a Service Manager for the Boss." One of my recent ideas (omitted from the original post in the interest of brevity) was that perhaps a new way of wrapping code is needed. Perhaps pida is showing the way. Is it possible, from pida, to access individual Emacs c or elisp functions? It's not clear whether being able to execute any elisp command would suffice. Edward
