Greetings, > In principle, I can see an advantage to being inside xemacs --- you can > tap into the editor's editing power, and you don't have to write a text > editor of your own.
Yes, there's some vague plan for a GUI. But I think there are still some questions to consider before work takes off. In some sense, we can ask: is it a _text_ editor we need? Or something else? What kind of tool will best support the process? FYI: I've got a prototype front-end in WxHaskell which supports some of the editing operations Epigram seems to require. It uses text entry boxes for sheds (solves the "editor" issue, in the small?), and is able to lay out horizontal and vertical nestings of sheds and/or text, plus draw inference rules. But there's some non-trivial things to work out still, eg interaction with syntax, and communication with the Epigram core. Paul
