Readline-style line-editor for Common Lisp.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
ports Fix 'Unbound variable: LINEDIT::ORIGINAL' Apr 4, 2018
.gitignore Consolidate documentation in README.md. Update project URL. Apr 13, 2018
LICENSE
README.md
TODO Replace UFFI with CFFI and eliminate C glue Mar 1, 2016
backend.lisp don't re-announce on reload unless something changes May 3, 2011
buffer.lisp persistent history and killring Jan 20, 2012
command-functions.lisp slice of untabification Jun 23, 2012
command-keys.lisp 0.17.3: history searching May 3, 2011
complete.lisp
dumb-terminal.lisp Slightly less broken paren matching. Nov 9, 2003
editor.lisp implement Toggle-Insert Jun 23, 2012
line.lisp * <blush>Type Julian's name correctly</blush> Apr 25, 2004
linedit.asd Consolidate documentation in README.md. Update project URL. Apr 13, 2018
main.lisp
matcher.lisp * <blush>Type Julian's name correctly</blush> Apr 25, 2004
packages.lisp Replace UFFI with CFFI and eliminate C glue Mar 1, 2016
rewindable.lisp
smart-terminal.lisp 0.17.4: allow setting highlight color May 3, 2011
terminal-glue.lisp Merge pull request #10 from khirbat/cffi Apr 2, 2018
terminal-translations.lisp
terminal.lisp
utility-functions.lisp
utility-macros.lisp

README.md

Linedit is a readline-style library written in Common Lisp that provides customizable line-editing for Common Lisp programs.

Linedit is basically portable between implementations, but most development and testing has so far been carried out on SBCL - but CCL at least is expected to work as well.

The canonical place to get linedit is

https://github.com/sharplispers/linedit

but unless you want to hack on linedit you should take the Quicklisp version! To report a bug submit a GitHub issue at the above URL. For patches please submit a pull request from a topic-branch.

Features

  • single-line text reader
  • multi-line form reader
  • completions on packages and symbols in current image
  • completions on directories and filenames
  • apropos-word and describe-word
  • unlimited undo
  • unlimited kill-ring
  • unlimited history
  • paren matching (not across lines)
  • multiple histories
  • use in REPL on SBCL and Clozure CL
  • paging
  • fully customizable in CL
  • works on Linux, FreeBSD, macOS

Usage

> (ql:quickload "linedit")

> (linedit:linedit :prompt "-> ")

> (linedit:formedit :prompt1 "=> " :prompt2 "|   ")

Meta-H in the prompt displays help. (Try ESC-H if your terminal misbehaves with meta-proper.)

Linedit in the REPL

SBCL and CCL only for now:

(linedit:install-repl :wrap-current t :eof-quits t)

in e.g. your Lisp initialization file (~/.sbclrc for SBCL). If you don't want to preserve your current input handler you can omit the WRAP-CURRENT keyword.

Documentation

function INSTALL-REPL &key wrap-current eof-quits

Installs Linedit REPL input handler. (SBCL and CCL only.)

function UNINSTALL-REPL

Removes Linedit REPL input handler. (SBCL and CCL only.)

function LINEDIT &rest keys &key prompt

Reads a single line of input with line-editing from standard input of the process and returns it as a string.

Results are unspecified if *STANDARD-INPUT* has been bound or altered.

:PROMPT specifies the string to print to *STANDARD-OUTPUT* before starting to accept input.

Further keyword arguments to LINEDIT are an advanced and undocumented topic, but if you're willing to dive into sources you can e.g. use multiple kill-rings not shared between different invocations of LINEDIT, or change the function responsible for providing input completion.

function FORMEDIT &rest keys &key prompt1 prompt2

Reads a single form (s-expession) of input with line-editing from standard input of the process and returns it as a string.

Results are unspecified if *STANDARD-INPUT* has been bound or altered, or if READTABLE is not the standard one.

:PROMPT1 specifies the string to print to *STANDARD-OUTPUT* before starting to accept input.

:PROMPT2 specified the string to print to *STANDARD-OUTPUT* when input spans multiple lines (prefixing every but first line of input from the user perspective.)

Further keyword arguments to FORMEDIT are an advanced and undocumented topic, but if you're willing to dive into sources you can e.g. use multiple kill-rings not shared between different invocations of FORMEDIT, or change the function responsible for providing input completion.