3 ms·
If you have used a Lisp Machine with something like Zmacs for an extended time, then one often manipulates with the mouse. Same sequence: mark, execute. For som
by lispm 12y ago
If you have used a Lisp Machine with something like Zmacs for an extended time, then one often manipulates with the mouse. Same sequence: mark, execute. For some things there is also modifier-click on something visual which creates a region.
Thus the whole select the object, execute sequence is the same:
* emacs keystrokes
* mouse manipulation
* Lisp functions: get the arguments, execute a function
Thus it is a very consistent model.
- agumonkey 12y agoUnfortunately I never had such pleasure. I understand a little more the appeal to have consistency between mouse and keyboard operations. Maybe I'm more a schemer than a lisper then because even though the function call protocol is eval args, eval body, one of the nicest thing about lisps is higher order functions. Vi feels exactly like this; a move is an abstract operation that can live on its own, or be passed to another abstract operation to be combined. To the extreme it reminds me of point-free programming where you dont even pass ~toplevel arguments, you just accumulate hof.