--> ap/xxxxx


eev bits: (emacs#21)

1] Installation: untar in its own directory. ./eev-rctool prepare and ./eev-rctool install_rc

2] Brief use:


find-node, find-fline, find-efile, find-enode (for Emacs Lisp), find-eevfile

eg: (find-node "(emacs)Lisp Eval" "C-x C-e")

is equivalent to:

(find-enode "Lisp Eval" "C-x C-e") which both search info node for that string

M-e to execute Emacs Lisp in middle of line

M-k kill newly opened buffer

M-x ee to write standard marked code to be executed by the shell using the ee command

M-h M-f as also of interest to generate hyperlinks about an Emacs Lisp function

C-q C-o created the red star delimiter character which can be used to mark blocks of text/code (hash star) for later execution using F3 in block

From 15. Communication channels of: http://angg.twu.net/eev-current/article/eev.txt.html

The way that we saw to send commands to a shell is in two steps: first we use M-x eev in Emacs to “send” a block of commands, and then we run `ee' at the shell to make it “receive” these commands. But there is also a way to create shells that “listen” not only to the keyboard for their input, but also to certain “communication channels”; by making Emacs send commands through these communication channels we can skip the step of going to the shell and typing `ee' - the commands are received immediately.


Eev binds F9 to a command that operates on the current line and then moves down to the next line; if the current line starts with star then what comes after the star is considered as Lisp code and executed immediately, and the current line doesn't start with star then its contents are sent through the default communication channel, or though a dummy communication channel if no default was set.