When you have run-picolisp started (thats an emacs buffer with pil repl), there are several additional options in the dropdown to evaluate the picolisp code where the cursor is in the editor buffer, or to run marked s-expressions.
You might be also interested in using emacs-like editing within the pil-repl: http://picolisp.com/wiki/?emacsstyleled
@Alexis:
Just have a look into lib/el/ in your picolisp installation. Maybe your efforts aren't really necessary (but surely a good exercise anyway).
I'm using the picolisp-mode coming with the picolisp distribution, and I'm really happy with it, especially since I use "paredit" with it.
Though I actually don't use the provided pil repl inside emacs but an additional terminal window (with http://i3wm.org).
Maybe you should rename your emacs extensions, so it doesn't get mixed up with the one coming with the picolisp standard distribution.
----- Original Message -----
From: Lawrence Bottorff [mailto:borg...@gmail.com]
To: picolisp@software-lab.de
Sent: Thu, 12 Feb 2015 08:24:11 -0500
Subject:
Okay, now it's working! Thanks for all your efforts!
As far as the drop-down menu, I can't recall. But it was present with the distribution package, in .../lib/el if I'm not mistaken. It's just that now when I run M-x picolisp-mode . . . nothing seems to have happened. For opening a *.l file, I get "Lisp Paredit Slime Projectile[picolisp] adoc" in my mode minibuffer. The original picolisp-mode.el instructions warned that *.l would be grabbed by slime. . . .
On Thu, Feb 12, 2015 at 6:54 AM, Alexis <flexibe...@gmail.com> wrote:
This is /after/ you've set the value of `picoliso-pil-executable` appropriately?
Lawrence Bottorff writes:
Okay, this is what I get with the latest melpa picolisp-mode:
emacs-snapshot: /usr/bin/pil: No such file or directory
Process picolisp-repl exited abnormally with code 127
