CIEL is an extended CL
Find a file
vindarel eba9f86cff Naming: the core is ciel-core, the binary is ciel
previously: ciel and ciel-repl
2022-12-09 14:27:28 +01:00
.github (minor) .github 2021-08-10 16:12:25 +02:00
docs Naming: the core is ciel-core, the binary is ciel 2022-12-09 14:27:28 +01:00
src repl: add disable-shell-passthrough (experimental) 2022-12-09 13:49:55 +01:00
.gitattributes add .gitattributes, don't count generated documentation as part of the project sources 2020-11-06 15:01:15 +01:00
.gitignore init 2019-03-23 13:04:03 +01:00
.gitlab-ci.yml (minor) typo 2022-12-09 13:45:03 +01:00
ABOUT.org REPL: very tolerant shell pass-through 2021-02-19 00:20:28 +01:00
build-image.lisp Naming: the core is ciel-core, the binary is ciel 2022-12-09 14:27:28 +01:00
ciel.asd Naming: the core is ciel-core, the binary is ciel 2022-12-09 14:27:28 +01:00
find-dependencies.lisp add FOF 2021-08-10 15:13:03 +02:00
Makefile Use Deploy's :deploy-console to silence its output (does it work?) 2022-12-09 13:44:33 +01:00
README.org Naming: the core is ciel-core, the binary is ciel 2022-12-09 14:27:28 +01:00
repl-utils.lisp REPL, visual commands: allow "sudo" and "ENV" modifiers 2021-02-18 23:08:34 +01:00
repl.lisp repl: add --noinform (prepare for scripting) 2022-12-09 14:18:05 +01:00
shell-utils.lisp Developer utilities: add Quicksearch 2022-01-07 17:41:20 +01:00

Install

You will probably need the following system dependencies (names for a Debian system):

libmagic-dev libc6-dev gcc  # from magicffi

With Quicklisp

You need a Lisp implementation and Quicklisp installed.

CIEL is not yet on Quicklisp, but it is on Ultralisp.

So, either clone this repository:

git clone https://github.com/ciel-lang/CIEL ~/quicklisp/local-projects/CIEL

either install the Ultralisp distribution and pull the library from there:

(ql-dist:install-dist "http://dist.ultralisp.org/" :prompt nil)

Then, load the .asd file (with asdf:load-asd or C-c C-k in Slime), quickload "ciel":

(ql:quickload "ciel")

and enter the ciel-user package:

(in-package :ciel-user)

With a core image

You need a Lisp implementation, but you don't need Quicklisp.

Build a core image for your lisp with all CIEL's dependencies:

sbcl --load build-image.lisp

and use it:

sbcl --core ciel-core --eval '(in-package :ciel-user)'

Then you can configure Slime to have the choice of the Lisp image to start. See below in /mirrors/ciel/src/commit/eba9f86cffbe3994663ca8ac3c4ea02b6ca0eac0/%2AUse%20CIEL%20at%20startup

We will distribute ready-to-use core images can not distribute core images, you must build it yourself.

With a binary. Use CIEL's custom REPL.

You don't need anything, just download the CIEL executable and run its REPL. You need to build the core image yourself though.

TODO: build it for different platforms.

To build it, clone this repository and run make build.

Start it with ./ciel.

You are dropped into a custom Lisp REPL, freely based on sbcli.

This REPL is more user friendly than the default SBCL one:

  • it has readline capabilities, meaning that the arrow keys work by default (wouhou!) and there is a persistent history, like in any shell.
  • it has multiline input.
  • it has TAB completion.
  • it handles errors gracefully: you are not dropped into the debugger and its sub-REPL, you simply see the error message.
  • it has optional syntax highlighting.
  • it has an optional lisp critic that scans the code you enter at the REPL for instances of bad practices.
  • it has a shell pass-through: try !ls.
  • it has documentation lookup shorthands: use :doc symbol or ? after a symbol to get its documentation: ciel-user> (dict ?.
  • it has developer friendly macros: use (printv code) for an annotated trace output.
  • and it defines more helper commands:
  %help => Prints this general help message
  %doc => Prints the available documentation for this symbol
  %? => Inspect a symbol: %? str
  %w => Writes the current session to a file <filename>
  %d => Dumps the disassembly of a symbol <sym>
  %t => Prints the type of a expression <expr>
  %lisp-critic => Toggles the lisp-critic
  %q => Ends the session.

See more in the documentation.

Usage

Create a package and "use" ciel in addition of cl:

  (defpackage yourpackage
    (:use :cl :ciel))

You can also use generic-ciel, based on generic-cl:

  (defpackage yourpackage
    (:use :cl :generic-ciel))

generic-cl allows us to define our + or equalp methods for our own objects (and more).

Use CIEL at startup

You can enter the CIEL-USER package when you start your Lisp image from your editor.

A working, but naive and slow-ish approach is to add this in your ~/.sbclrc:

(ql:quickload "ciel")
(in-package :ciel-user)
(ciel-user-help)

A faster way is to use CIEL's core and to use SLIME's or your editor's feature to configure multiple Lisps.

You need to:

  • build CIEL's core for your machine (make image),
  • add this to your Emacs init file:
  (setq slime-lisp-implementations
        `((sbcl    ("sbcl" "--dynamic-space-size" "2000"))  ;; default. Adapt if needed.
          (ciel-sbcl  ("sbcl" "--core" "/path/to/ciel/ciel-core" "--eval" "(in-package :ciel-user)"))))
  (setq slime-default-lisp 'ciel-sbcl)
  • and start a new Lisp process.
  • optional: if you didn't set it as default with slime-default-lisp, then start a new Lisp process with M-- M-x slime (alt-minus prefix), and choose ciel-sbcl. You can start more than one Lisp process from SLIME.

The Lisp process should start as fast as the default SBCL.

Libraries

We import, use and document libraries to fill various use cases: generic access to data structures, functional data structures, string manipulation, JSON, database access, web, URI handling, GUI, iteration helpers, type checking helpers, syntax extensions, developer utilities, etc.

See the documentation.

To see the full list of dependencies, see the ciel.asd project definition or this dependencies list.

Language extensions

We provide arrow macros, easy type declaratons in the function lambda list, macros for exhaustiveness type checking, pattern matching, etc.

See the documentation.

Final words

That was your life in CL:

and now:

How to generate the documentation

See src/ciel.lisp and run (generate-dependencies-page-reference).