I'm starting a new thread because there doesn't seem to be a way of replying directly to such an old thread.
Robin's mission has been a powerful behind-the-scenes influence on my thinking. I've recently created a status report on Leo's google- groups site: http://groups.google.com/group/leo-editor This status report is very long: I'll just summarize it here. 1. The first post at http://groups.google.com/group/leo-editor/browse_thread/thread/4f76a0f57759aba is a verbatim repost of Robin's original post. 2. The second (long) post on the same thread is an item-by-item discussion of who Leo meets, or fails to meet, Robin's checklist. 3. The third (long) post is a discussion of how Leo goes far beyond Robin's checklist. The basic idea is that if all you want is Emacs, you know where to find it. To displace Emacs, an editor must offer *much* more than Emacs. This, Leo does, imo. I welcome any comments on http://groups.google.com/group/leo-editor/browse_thread/thread/4f76a0f57759aba here from pyxides folk. My guess is that it would be most comfortable to comment on Leo's site, but it's up to you. Finally, I'd like to invite Robin, once again, to start using Leo. Here is an excerpt from the third posting: QQQ the reason some of the items on Robin's list are week in Leo is because nobody uses them in Leo :-) For example, nobody cares about typing completion for file names in Leo's minibuffer because @thin or @button are far easier ways to open files. For more than seven years how I have been responding to requests from Leo's users. What has gotten done are what people have actually wanted, and almost nothing else. I plan to continue this strategy. OTOH, if Robin started using Leo and made requests, I would certainly listen very carefully :-) QQQ Edward -------------------------------------------------------------------- Edward K. Ream email: [email protected] Leo: http://webpages.charter.net/edreamleo/front.html --------------------------------------------------------------------
