[EMAIL PROTECTED] wrote: > I still don't understand.
I elaborated on some of these points in a post to Aaron Brady. If you missed it on the list, let me know and I will forward you a copy. It seems that you want to be able to do: > "END_CLASS" to end the current class. > > "END_DEF" to end the current function > > "END_BLOCK" to end anything else. > > This is possible with some emacs lisp but I don't see what this gains > you over > "BACK" "BACK" "BACK" > where "BACK" sends a backspace to emacs. > (Actually I'd define an "END" command which you could give at the > end of the last line of a block. That would relieve you of the need to > enter the newline and tab.) > Yes, it requires a few extra utterances on occasion, but you don't > have to worry about three new (multi-syllabic) verbs to recognize. > > Am I understanding your requirement correctly? no but it's not your fault. I have a bad habit of asking for the component that I need (i.e. gimme a six-inch 8-32 screw) without telling you what I need it for because it is extremely clear in my mind what I need the screw for (i.e. barn door mount for astrophotography). All of this navigation stuff was driven by the need to embedded inside of a larger command invoked through speech recognition. I have no conditionals about the environment so I can't tell whether I need to indent once or twice or three times to make it go to the right place. Remember, this is a component in a blind macro (i.e. one that is not aware of its environment) and therefore must operate correctly with no knowledge of its environment. Many of the features speech recognition users need from editors are these smart navigation commands so that one can perform more complex operations without worrying about indentation or position or things of that nature. my voice is wearing out. More later ---eric -- http://mail.python.org/mailman/listinfo/python-list
