hellerve / sbcli Goto Github PK

This is a TODO for myself to package sbcli for GNU Guix.

Blocked by: #28 and #29

At least here (load "utils.lisp") makes invoking sbcli only work inside its own directory; where should it go instead? to /usr/local/bin/ too? or just put its content inside repl.lisp?

The following interactive session says it all:

$ sbcli
Veit's REPL for SBCL version 0.1.4
Press CTRL-D or type :q to exit

sbcl> :help
Veit's REPL for SBCL version 0.1.4
Special commands:
  :h: Gets help on a symbol <sym>
  :help: Prints a general help message
  :doc: Print the available documentation for this symbol.
  :s: Writes the current session to a file <filename>
  :d: Dumps the disassembly of a symbol <sym>
  :t: Prints the type of a expression <expr>
  :q: Ends the session
  :r: Resets the session environment
Currently defined:
sbcl> :r

debugger invoked on a SB-KERNEL:SIMPLE-PACKAGE-ERROR in thread
#<THREAD "main thread" RUNNING {10046101B3}>:
  Package "SBCLI" is used by package:("SBCLI-USER")

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE] Remove dependency in other packages.
  1: [RETRY   ] Retry EVAL of current toplevel form.
  2:            Ignore error and continue loading file "/usr/local/bin/sbcli".
  3: [ABORT   ] Abort loading file "/usr/local/bin/sbcli".
  4:            Abort script, exiting lisp.

(DELETE-PACKAGE SBCLI)
0] 3

Am I missing something obvious?

I feel spoiled asking this, but my what I immediately realize when starting using sbcli with pygmentize, which sounded great, is that the contrast is really too low to be usable. I have a dark pastel theme in my terminal. I have never directly used pygmentize before testing sbcli, but I have now just tried to pygmentize a Python file to standard out, and it really looks horrible. I do not really want to spend more time on this right now (I want to spend time reading my Lisp book instead) but if you have any tips on getting a different color theme with sbcli and pygmentize, I'm all ears.

Otherwise, sbcli seems really neat. Thanks for sharing it.

Thanks for writing this wonderful thing!

I wonder if it's possible to interact with the debugger as in the usual sbcl. For now, by default, it seems that whenever an error (or a condition) occurs, sbcli prints the message to screen but does not let us choose what to do (e.g. ignore, accept, abort.. etc).

Hi @hellerve.

I'm trying to use pygmentize.

It output the help on the prompt and don't let use the CLI:

❯ sbcli
My LISP REPL version 0.1.3
Press CTRL-D or type :q to exit

> Usage: /home/max/.local/bin/pygmentize [-l <lexer> | -g] [-F <filter>[:<options>]] [-f <formatter>]

I'm on Linux with Python 3.8 and last Pygments version

Hello,

Currently typing package:sym will not complete "sym" from "package".

I see that cl-repl does that correctly.

I'm on it, rounding up edge cases.

Hi, thanks for making this project!

Would you accept a .asd file for this project?

Resolving this would also make it very easy to package sbcli for GNU Guix.

@vindarel I think that this issue might be related to #17

Hello!
Thanks for sharing this project, it's quite fun. Wondering, whether you have some specific use cases that this project covers the best or maybe, some vision/idea of what it should be?
Previously, I would be using rlwrap sbcl for some repl experiments. As I see now, thigs that sbcli is doing better (compared to rlwrap sbcl):

1. easier to customize prompt
2. using cl-readline means that it's possible to hook into completion via (rl:register-function :complete #'complete) and do autocomplete (which is missing from rlwrap sbcl combo, or I wasn't able to set it up)

doing worse:

1. no multiline input / paste
2. no restarts

(opened the issue to not forget)

Hi,

Thanks for making this project!

I think we should not make sbcli strictly depend on quicklisp by hardcoding quicklisp specific code at the top of the file.

There are other package managers for Common Lisp such as Nix, Guix, Roswell, etc. that require the project to be in a package manager agnostic format.