by billiob on 4/8/23, 9:31 PM with 28 comments
by nonfamous on 4/8/23, 11:06 PM
I do remember I had to use an awful hack to make it work. Comint expects data from a pipe, but eLisp output is internal to Emacs. The details are hazy now, I but I think I pushed the eval result as stdin to a ‘cat’ process for Comint to ingest the output. I wonder if that ever got cleaned up…
by neilv on 4/9/23, 3:24 AM
* Lisp Interaction mode (like in your `scratch` buffer). Press `C-j` to eval the expression to left of the point, and insert the result in your buffer. Then you can leave the result there, edit it into a new code, undo to hide it, etc.
* Emacs Lisp mode (like when you're editing any `.el` file) can also do a lot of things that people normally do in a REPL. Say, you're working on some code in the file, and it's running, and you want to change one of the functions. Just edit the function in the file, and hit `M-C-x` to evaluate the `defun` that the point is in, and see the value in the echo area. Or evaluate a region, or the entire file. (At one point, I also had a pretty-printer hooked up, so that it could do better transient display of values.) You can also selectively instrument functions for Edebug from here.
This seems simple today, but it used to blow away the development languages and tools most people were using.
by JimmyRuska on 4/9/23, 2:51 AM
by tadfisher on 4/8/23, 10:51 PM