On Feb 2, 8:41 am, "Edward K. Ream" <[email protected]> wrote: > This thread will discuss Robin Dunn's post, "Your mission, should you > choose to accept it"...I'll post my thoughts in responses to > this post.
Here is my present view about how Leo accomplishes this mission: ===== Mission accomplished * Python should be just one of the languages that this editor supports, not the primary target. * Absolutely every feature or action must be able to be done with just the keyboard. * Multiple top level windows, and able to show any buffer in any TLW, including those that are already displayed in another TLW. Comment: Leo goes *way* beyond this. * Registers. * A rectangle selection and paste. * Regex search. * Good keystroke macro recording and the ability to save and load keystroke macros, and the ability to assign a key-binding to a saved recorded macro. Comment: Experimental, but could be made much more usable than Emacs. * If you must have a toolbar make it optional and keep it simple. Comment: Leo shows that Robin's assertion that "Toolbars require the mouse" is incorrect. Toolbar items can easily create minibuffer commands. * Avoid using popup dialogs whenever possible. * So I would prefer this editor to have something like emacs' minibuffer. * For access to editor commands/functionality that may not be bound to a keystroke it's real nice to have the ability to hit a key, type the command name, press enter and then it's done. This can also allow for commands that might need to prompt for parameters, be interactive, etc. All editor commands should be named and can be bound to keys by name or executed by name in this way. * If it is a full IDE it would be nice to have a way to start just the code editor portion for quick edits. * Able to be a front-end for gdb. * Able to be a front-end for CVS, SVN, etc. * Be able to run shell commands, or the shell itself in an editor buffer. * have a built-in psychotherapist or be able to play towers of hanoi. ;-) ===== Maybe done. * The Kill-Ring. Comment: lightly used. Could be improved. * Typing completion for file dialogs. Comment: lightly used, because @file nodes reduce the need for this. ===== Not done. * Incremental search, both forward and reverse, and wrapping around after you've reached the end or the beginning of the document. Comment: I plan to start work on this immediately. * [Added by EKR] typing completion for Leo itself works well enough, and it will be further improved this year. ==== Not done, but could be done in @command easily enough * Flexible build/grep commands. * Multi-file search and replace. * Interactive diffs, merges and applying of patches. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
