cl-repl VS clesh

But you don't have syntax highlighting :( On errors, the debugger looks arcane… cl-repl or sbcli might help. With sbcli, you even don't have the interactive debugger, only the stacktrace. It's easier for beginners (or for quick development). They are based on readline and do some things well (match parenthesis, multiline input for cl-repl).

In order to get syntax highlighting as well as tab completion I have been using cl-repl. I have been having this issue, as well as another issue with cl-repl inheriting some stuff, but do not seem to have the same issue in sbcl either. Could it be a bug in cl-repl? Is there a solid alternative for sbcl?

If you are doing it for learning, that's fine! But otherwise you could check out and contribute to Alive for VSCode. There's also cl-repl which I think can be distributed in the form of binary images.

Then, of course, a solution is to run the scripts from our editor… or from a friendly terminal-based interface? There's Lish, the Lem editor (for CL, Python and other languages), friendly REPLs… (cl-repl)

Now, it's only personal, but I like to fire one-off shell commands… can we escape the Lisp REPL or not? If not, we could use a shell pass-through, for example "! ls" with clesh. Ruricolist's cmd is nice to have too. This is becoming an heresy, but what if we could fire a shell command and interpret its result with a Lisp function, or mix and match the two? Lish is doing an awesome work already, although it's a difficult field. Interactive commands like sudo and htop work there, at least. It ships a Lisp REPL and a debugger for the terminal too (similar to Roswell, then).

Clesh - extends Common Lisp to embed shell code in a manner similar to perl's backtick. (I read awesome-cl) It could ease the process to include external calls.