The MIT Lisp Machine Lisp Listener

Evidence sets

Purpose and entry points

The System 46 operations manual calls the Listener the first full-screen window after a cold boot and the usual place to run simple user programs. Its core operation is a conventional read-eval-print loop: read one Lisp form, evaluate it, and print every value.

Ways to obtain or select a normal Listener include:

• cold boot, which creates the initial full-screen Listener;
• System L, which selects an existing Listener and normally creates one if none exists;
• Control-System L in System 303, which explicitly requests a new one;
• Lisp in the System 303 System Menu's Programs column;
• Create, then Lisp, in the System Menu;
• code that constructs TV:LISP-LISTENER or asks TV:IDLE-LISP-LISTENER for an idle full-sized Listener.

System L is a selector, not an evaluator command. Repeating it cycles through the most recently selected windows recognized as Listeners. The related System Menu and selector article documents that registry and cycling algorithm.

The window and the Lisp top level are separate layers

SI:LISP-TOP-LEVEL1 implements the read-eval-print semantics. The window system supplies a stream and process that run it. This split permits the same top-level function to operate over different streams, while the LISP-LISTENER flavor supplies the visible, selectable embodiment.

In System 303, the flavor hierarchy makes several boundaries explicit:

• LISTENER-MIXIN-INTERNAL owns the top-level process but is deliberately invisible to System L;
• LISTENER-MIXIN adds recognition by System L;
• LISP-INTERACTOR is a Lisp interaction window built on the internal mixin, but its source documentation explicitly says it is not a normal LISP-LISTENER-P;
• LISP-LISTENER combines notification handling, the public Listener mixin, and a saved-bits window;
• IDLE-LISP-LISTENER reuses an idle Listener of the requested full-screen size or constructs one when necessary.

The process preset gives the top level a regular PDL size of 40,000 and a special PDL size of 4,000 in both inspected lines. LISP-LISTENER-P reports :BUSY while LISP-TOP-LEVEL-INSIDE-EVAL is true in that process's stack group and :IDLE otherwise.

System 303 also delays starting many window processes until the window will actually become visible. The source explains that this reduces boot paging and prevents partially initialized editor windows from running too early. A nearby comment calls this process/window selection machinery a “horrible crock” that ought to be replaced by a program system. That is implementation evidence of a known architectural boundary, not a museum characterization of the whole system.

Per-Listener package and reader state

The System 303 top level synchronizes its dynamic *PACKAGE* with a package slot on the terminal stream. If Lisp code changes *PACKAGE*, the window is updated; if another operation changes the window's package, the next top-level iteration adopts it. The first iteration initializes whichever side has not yet been set.

The loop also binds the readtable, print base, and read base for its own execution. When the readtable changes, it reports the current input base, package, and readtable. The observed System 303 Listener printed:

;Reading at top level in Lisp Listener 1.
;Reading in base 10 in package USER with standard traditional syntax readtable.

This per-window package synchronization is absent from the inspected System 46 LISP-TOP-LEVEL1; it should not be retroactively attributed to that snapshot.

Interaction histories and multiple values

Both implementations preserve recent forms and values as dynamically bound Listener variables, but System 303 extends the model.

System 303 pushes an entry on *VALUES* even when evaluation aborts; the entry is NIL in that case. Its top level prints each value on a separate line. A fresh runtime evaluation of (values 7 8) visibly printed 7 and 8 on successive lines, confirming the multiple-value path in the loaded band.

The break loop reuses these histories rather than creating an unrelated REPL state. In System 303, Resume continues, Abort quits the break, and a form of the shape (RETURN value) returns that value from the break context.

Buffered Listener input editor

The Listener does not use ZWEI for its ordinary input. It uses the window stream's rubout handler, a buffered editor that rescans the form after edits. Ordinary characters insert themselves. Because Lisp forms are self-delimiting, a Return that supplies terminating whitespace normally lets READ finish; End is also declared as an explicit activation character in System 303's READ-FOR-TOP-LEVEL.

“Does not use ZWEI” needs one qualification. The System 303 input editor is its own rubout-handler implementation and does not create a ZWEI buffer, but it shares ZWEI's input-history, kill-history, syntax tables, argument-list printer, and documentation machinery when those facilities are loaded.

Mouse and global keyboard behavior

The Listener itself gives the mouse no application-specific object gestures. The System 46 manual describes its pointer as the ordinary north-by-northwest arrow and says a single right click summons the System Menu. The System 303 runtime who-line repeated the same instruction: Click right to get the System Menu.

Global keyboard interception still applies. Abort returns a computation to the Listener command level, Break enters a break loop, Help invokes global keyboard documentation, and System and Terminal introduce window-system commands. These are window-system facilities that operate while the Listener is selected; they are not additional rubout-handler bindings.

Runtime observation: System 303-0

The Xvfb computer-use harness made a fresh, non-resumed boot and preserved the following boundary:

The ordered relevant input was: answer the boot date/time questions with N (one early second N was sent before the second prompt and had no visible effect, so the answer was sent again), evaluate (values 7 8), open the System Menu with right click, request System Help, select System I, inspect '(museum listener inspector peek), select System P, choose Active Processes, open the first process's action menu, dismiss it without choosing an action, and stop the emulator.

The Listener multiple-value capture is 768×963 with PNG SHA-256 139d66a2ddc3230e46781610a079a0e0134bf440becaa665f9c2042d514d551c and decoded-pixel SHA-256 428ce18e58cbda778a5e33e216f946ada4f8ef1a401961024b085e7f95b90b04. The image-specific publication review approved this one sparse state and mapped it to the curated CADR screenshot catalog.

Runtime observation: the Lisp Listener in LM-3 System 303 after evaluating (values 7 8), captured 2026-07-18. Underlying software and display material remain the property of their respective rightsholders; reproduced here for criticism, scholarship, and historical documentation under 17 U.S.C. section 107. No affiliation or endorsement is implied.

The 6,781-byte run record has SHA-256 2d877843f58a8a261bafe68afca846919963dec5584a39bbb5275fcbe6615e22. Shutdown was clean: forced_stop and state_may_be_incomplete are false, the emulator and Xvfb exited zero, and the base disk was unchanged. See the computer-use harness article for the evidence schema.

What the manual alone does not establish

• The operations manual's short Listener chapter accurately identifies a REPL, but it does not describe the per-window process, idle/busy query, package synchronization, value histories, or the standard input editor's movement, kill, history, completion, and context-help command sets.
• A Listener-shaped interaction pane is not necessarily selectable by System L; System 303 deliberately distinguishes internal listener mixins and LISP-INTERACTOR from public Listeners.
• System L selecting a Listener does not imply that it creates a new one on every invocation. Normal selection cycles existing windows; explicit creation is a separate path in System 303.
• The observed System 303 package and history behavior must not be projected backward onto System 46 where the corresponding code differs.

Open questions

• No System 46 load band was run for this article. Its visible prompt shape, exact old-keyboard echo behavior, and any patches applied beyond the pinned source remain source-grounded rather than runtime-confirmed.
• The System 303 run exercised ordinary evaluation, multiple values, and program selection, but did not deliberately trigger a parse error or nested break loop, nor did it exercise each full rubout-handler movement, history, completion, and context-help command. Those paths are established by source and should be sampled in a future non-destructive runtime session.

Sources

• MIT CADR System 46, ltop.231, baswin.428, stream.14, and operations manual source, revision 8e978d7; verified 2026-07-18.
• LM-3 System 303, ltop.lisp, sysdcl.lisp, baswin.lisp, stream.lisp, rh.lisp, and read.lisp, check-in 4df393c; verified 2026-07-18.